Development method for integrated circuits, program storage medium for storing the development method for integrated circuits, and concurrent development system, development program, and development method of ASIC and programmable logic device

ABSTRACT

A method for developing integrated circuits includes generating a core (logic core) in an HDL format readable by a logic synthesis tool, from an ASIC core (logic core) made of ports of blocks and port connection information, creating a temporary chip design from chip terminal information to generate a terminal in the temporary chip design, generating a design identical to that created, as a cell within the design created, connecting a design port with a cell port, wherein a name of the design port is identical to a name of the cell port, inserting an I/O buffer, depending on the device technology, into a net between the ports connected, replacing the cell by the core (logic core) created to gerate a netlist, and expanding a hierarchy of the design, being the top hierarchy.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a divisional of application Ser. No. 11/636,606,filed Dec. 11, 2006 now U.S. Pat. No. 7,647,575, and now allowed, whichis related to concurrently filed application Ser. No. 11/636,607, filedDec. 11, 2006, and now allowed, both of which are divisionals ofapplication Ser. No. 10/965,850, filed Oct. 18, 2004, and now U.S. Pat.No. 7,219,311, which is a continuing application, filed under 35 U.S.C.§111(a), of International Application PCT/JP03/04787, filed Apr. 15,2003, which further claims the benefit of priority Japanese PatentApplication Nos. 2002-115273, filed Apr. 17, 2002 and 2002-147930, filedMay 22, 2002, the contents of which are incorporated herein byreference.

TECHNICAL FIELD

The present invention relates to a programmable logic device formingmethod for development of integrated circuits, and a development methodfor developing integrated circuits, a program storage medium for storingthe development method for integrated circuits, a controller for a logicsynthesis tool, a concurrent development system, a concurrentdevelopment program, and a concurrent development method for concurrentdevelopment of the ASIC and the programmable logic device, which enableseamless and concurrent development of the ASIC and the programmablelogic device, ensure the design quality while reducing the developmentperiod, human resources, and development cost.

BACKGROUND ART

In the manufacturing procedure of integrated circuits, thespecifications are determined, and designing is performed according tothe specification, after having examined carefully if anything has beenoverlooked. FIG. 11 is a flowchart of the procedure for designingintegrated circuits. First, the specification of an Application SpecificIntegrated Circuit (ASIC) is obtained from the product specification(step g1). Circuit architecture is then studied (step g2). Circuitdesigning is then performed based on the study of the circuitarchitecture (step g3). This circuit designing is performed whileperforming logic verification (step g4).

After circuit designing, logic synthesis of the circuit is performed(step g5). Next, layout expansion is performed based on the logicsynthesis (step g6). At this stage, the circuit design is complete. Whenthe circuit is designed, the circuit is manufactured (step g7), and areal machine is evaluated by using the produced circuit (step g8). Inthe above sequence, the present invention is related to the logicsynthesis at step g5.

In the development of integrated circuits, a circuit architecture studyfor studying a function to be realized using the specification as aninput, and studying the circuit configuration for realizing the functionis executed in the following flow. Normally, in the development of theintegrated circuits, functions for realizing a product are extractedwithout omission from the product specification, and a study of acircuit configuration for realizing the dug up functions and a macrostudy such as Intellectual Property (IP) are executed. Macro here refersto the one including the IP that can be used without changing a RAM, aROM, or the like.

Initial estimate for a circuit for which the configuration has beenstudied, and the size of the IP to be realized is performed, bycalculating the number of gates if known at this stage, and if thenumber of gates is not known, the number of flip-flops is calculatedfrom the required number of signals and the time required for theprocessing, to estimate the size to be realized. A plurality offunctions is grouped to form one block, based on the estimated size andthe number of input/output signals (hereinafter, “ports”) for therespective functions. This grouping is performed for all functions.

In the logic design, a circuit is designed for a programmable logicdevice by a means such as Hardware Description Language (HDL) based onthe functions and the estimated size, to perform on-board functionevaluation. After having finished the evaluation, redesign andreevaluation are performed at the time of forming the ASIC.

After completion of the function evaluation, when cost reduction isrealized by forming the ASIC, designing taking the ASIC intoconsideration is not normally performed at the time of designing theprogrammable logic device (for example, FPGA). Therefore, redesign isrequired for the ASIC based on the design data of the programmable logicdevice, due to differences between the ASIC and the programmable logicdevice, like a macro such as an I/O buffer, a device test circuit, and amemory. This results in problems such as double management of designdata due to redesign, prolonged development period and an increase inthe development cost due to redesign and reevaluation of functions.

The ASIC has a feature of prolonged development period but low cost, andin contrast, the programmable logic device (FPGA) has a feature of shortdevelopment period but high cost.

The present invention has been made in consideration of the aboveproblems, and it is an object of the present invention to provide adevelopment method of integrated circuits, to which a method of creatinga netlist between blocks as port connection information from portinformation of blocks obtained by functionally dividing a chip and portinformation of the chips (disclosed in Japanese Patent ApplicationLaid-Open No. 2000-90142) is applied, in the circuit architecture studyapplied for logic design, logic synthesis, and concurrent (parallel)development of a layout in the development of a large-scale ASIC, and anapparatus that controls a logic synthesis tool so that blocksconstituting the integrated circuit to be developed by the developmentmethod of the integrated circuits and a net between blocks are formed inan optional size and optional number from the netlist between blocks. Itis further an object of the present invention to realize a commonarchitecture, and provide a development method of integrated circuitsthat can avoid redesign and re-verification as much as possible, and aprogram storage medium for storing the development method of theintegrated circuits.

Recently, even an ASIC with 10M gates or more have been developed bymicrofabrication of a semiconductor. However, with the electronicequipment becoming high-function and complicated, implementation designfor performing specification design, logic design, floor plan, logicsynthesis, layout design, and timing verification requires long time andit becomes difficult to ensure the design quality. Particularly, remakeof the ASIC development not only extends the development period ofelectronic equipment, but also increases cost and a loss of marketinvestment opportunity.

Therefore, a programmable logic device having a short development turnaround time (TAT) and an easy-to-change design is used in manyoccasions, but the programmable logic device is expensive, and itsdownsizing is difficult. Accordingly, in many occasions, functions arerealized first by the programmable logic device, and after debugging byprototyping, the ASICs are formed at the time of mass-production.

However, even if verification is performed by prototyping of theprogrammable logic device with the assumption of forming the ASIC, thereis a problem in the serial development from the programmable logicdevice to the ASIC in that it is difficult to shorten the entiredevelopment process. Particularly, when a timing problem occurs in theimplementation design at the time of developing the ASIC, there is thepossibility that redesign of the programmable logic device must beperformed again. Consigning the design to outside the company, such as asemiconductor vendor, causes an increase in the cost as well as in humanresources in the consignee.

Further, when redesign takes place exclusively in the ASIC due to adifference in the structure between the programmable logic device andthe ASIC device, not only does debugging by the programmable logicdevice become meaningless, but also the development period is prolongedto thereby cause a cost increase. In either case, it causes a loss ofmarket investment opportunity.

As a measure against the prolonged development period accompanying alarge scale ASIC, as disclosed in Japanese Patent Application Laid-OpenNo. 2000-90142, circuit architecture study, logic design andverification, and implementation design are concurrently performed.However, specification design, logic design and verification areprolonged due to complicated functions of the electronic equipment andfast market movement, and hence it becomes difficult to shorten thedevelopment process. Further, when the development is executedconcurrently, human resources having the knowledge of ASIC developmentand a development tool are necessary, thereby causing a problem in thattraining about the development tool, which becomes complicated with theprogress of the semiconductor technology, becomes necessary.

Therefore, it is also an object of the present invention to provide aconcurrent development system, a concurrent development program, and aconcurrent development method of the ASIC and the programmable logicdevice, which enable seamless and concurrent development of the ASIC andthe programmable logic device, ensure the design quality while reducingthe development period, and can reduce human resources and cost requiredfor the development.

DISCLOSURE OF THE INVENTION

A program storage medium that stores a development method for developingintegrated circuits, the development method includes a core generatingincluding generating a core (logic core) in an HDL format readable by alogic synthesis tool, from an ASIC core (logic core) made of ports ofblocks and port connection information, by a unit that selects optionalblocks having a connection to group the blocks, wherein the core (logiccore) includes ports of blocks of optional size and number and portconnection information, creating a temporary chip design from chipterminal information by using the logic synthesis tool to generate aterminal in the temporary chip design, a design generating includinggenerating a design identical to that created at the creating, as a cellwithin the design created, connecting a design port with a cell port,wherein a name of the design port is identical to a name of the cellport, inserting an I/O buffer, depending on the device technology, intoa net between the ports connected, and a netlist generating/expandingincluding generating a netlist by replacing the cell by the core (logiccore) created at the core generating, and expanding a hierarchy of thedesign, being the top hierarchy.

According to one aspect of the present invention, a computer readablerecording medium for storing a program for making a computer execute amethod is provided, wherein an entity, being a port specification of ablock is created from a port name, range, and input/output definition,and output to a file (written in a file). It is then checked whetherthere is no mistake in an output port name of an instance on the outputside specified as an input port of a certain block by a unit thatcreates an output signal file relating to a port defined as output bythe input/output definition. When there is a definition of keyword inthe instance name on the output side, such as I/O indicating connectionwith a terminal of a device package, an entity, being a portspecification of a core (logic core), is created and written in a file,by a unit that determines whether the terminal is one or multiple(vector) from the range definition, a unit that determines whether theterminal is for an input or an output from the input/output definition,and a unit that determines whether the terminal is a two-way terminalfrom the type definition, by designating a name in the output port nameof the instance on the output side as a terminal name of the devicepackage. The “instance” here stands for a circuit unit.

When a port of the block is defined as input by the input/outputdefinition, it is checked whether there is a set of the instance name onthe port output side and an output port name of the instance on theoutput side in the output signal file. When it is determined thatconnection of ports between the instances is possible, a signal forconnecting the instances is created, and written in the file. When theprocess including the check of all instances has finished, the entity ofthe core (logic core) and the net between the instances are read, tocreate a core (logic core), which is then written in the file.

If there is no problem in the check result, an HDL file (hereinafter,“core (logic core)”) that includes the input/output port specificationof the block, the connection net between the instances, and a connectionnet between the instances and external terminals, being terminals of thedevice package, and does not have a logic design part at all, is output.

According to the above aspect, in a program storage medium that stores aprogram for making a computer execute a method of generating a core(logic core), the quality of port specification of a block, being aninput in the RTL design, is ensured beforehand in the integrated circuitdevelopment. Further, in a large-scale integrated circuit having manyfunctional blocks and design resources, because connection betweenblocks can be confirmed beforehand, it can be ensured that a chip isassembled without fail.

According to another aspect of the present invention, a developmentmethod for developing integrated circuits, to be used when concurrentdevelopment of an ASIC and a programmable logic device is conducted,includes a core generating including generating a core (logic core)including ports of blocks of optional size and number and portconnection information, from a netlist referred to as an ASIC core(logic core) made of ports of blocks and port connection information, bya unit that selects optional blocks having a connection to group theblocks, creating a temporary chip design from chip terminal informationby using a logic synthesis tool, a terminal generating includinggenerating a terminal, with a name existing in the chip terminalinformation, in the temporary chip design, a design generating includinggenerating a design identical to that created at the creating, as a cellwithin the design created, connecting a design port with a cell port,wherein a name of the design port is identical to a name of the cellport, inserting an I/O buffer, depending on the device technology, fromthe chip terminal information into a connection net, replacing the cellby the core (logic core) created at the core generating, and a chipnetlist generating including generating a chip netlist by expanding ahierarchy of the design created at the creating, being the top hierarchyof the core (logic core).

The invention according to the above aspect is a development method ofintegrated circuits wherein in the concurrent development of the ASICand the programmable logic device, the method includes steps ofcontrolling functions of a logic synthesis tool by a controller in whicha program storage medium that stores a program for making a computerexecute a netlist creation method according to claims 3 and 4 is loaded,from the core (logic core) of the ASIC according to claim 1, groupingoptional blocks having a connection, cutting the grouped blocks as acore (logic core) of the programmable logic device, and inserting an I/Obuffer depending on the programmable logic device, to create a netlistof chips for the programmable logic device.

According to the above aspect, a core (logic core) of the programmablelogic device is allocated from the ASIC core (logic core), whilemaintaining connection between blocks. Therefore, if verification of theprogrammable logic device using the core (logic core) is performed,duplication of verification at least in the same configuration can beavoided in the ASIC. Thus, concurrent development of the ASIC and theprogrammable logic device can proceed efficiently.

When inserting the I/O buffer, the chip port information defined in theblock and the chip terminal information can be cross-checked by a unitthat generates a temporary core (logic core) from the chip terminalinformation, and replaces it by a core (logic core) generated from theblock, thereby ensuring the quality of the port specification of theblock and the chip terminal specification.

According to still another aspect of the present invention, the programstorage medium according to claim 1, wherein in the development method,the core generating further includes creating a netlist, including portsof blocks of optional size and number and port connection information,from the ASIC core (logic core) made of ports of blocks and portconnection information, by the unit that selects the optional blockshaving the connection to group the blocks.

As a result, a netlist including ports of blocks of optional size andnumber and port connection information can be created.

According to still another aspect of the present invention, in a programstorage medium that records a development method for developingintegrated circuits, the development method includes a core generatingincluding generating a core (logic core) including ports of blocks ofoptional size and number and port connection information, from an ASICcore (logic core) made of ports of blocks and port connectioninformation, by a unit that selects optional blocks having a connectionto group the blocks, creating a temporary chip design from chip terminalinformation by using a logic synthesis tool to generate a terminal, witha name existing in the chip terminal information, in the temporary chipdesign, a design generating including generating a design identical tothat created at the creating, as a cell within the design created,connecting a design port with a cell port, wherein a name of the designport is identical to a name of the cell port, inserting an I/O buffer,depending on the device technology, from the chip terminal informationinto a connection net, replacing the cell by the core (logic core)created at the core generating, and a chip netlist generating includinggenerating a chip netlist by expanding a hierarchy of the design createdat the creating, being the top hierarchy of the core (logic core).

As a result, a chip netlist can be created from the netlist includingports of blocks of optional size and number and port connectioninformation.

According to still another aspect of the present invention, in thedevelopment method of integrated circuits, when a netlist includingports of blocks of optional size and number and port connectioninformation is created, a port name in the top hierarchy, being a netname, is corrected to match with a port name of a block to be connected,thereby creating a netlist made of ports of blocks and port connectioninformation.

The invention according to the above aspect is a control method of alogic synthesis tool, wherein in the concurrent development of the ASICand the programmable logic device, when optional blocks having aconnection are grouped from the core (logic core) of the ASIC includingthe block ports and connection information of the ports, and are cut asthe core (logic core) of the programmable logic device by using thefunction of the logic synthesis tool, the port name at the top of thecut core (logic core) is normally a name of a net connected to the port,the net is traced from the port to the inside of the core (logic core)by controlling the function of the logic synthesis tool, which replacesthe port name of the first found block.

According to the above aspect, in a recording medium that stores aprogram for making a logic synthesis tool execute a method of generatinga core (logic core) of the programmable logic device, a decrease inefficiency of debugging such as logic verification can be prevented whena net name, from which it is difficult to determine the function of aport, becomes a port name.

Thus, the circuit architecture can be shared by generating a core (logiccore) from the design document data and newly generating a core (logiccore) for the programmable logic device from the core (logic core), withthe hierarchical structure and the connection information beingpreserved. The circuit data and the net between instances, which do notdepend on the device technology in the instance in which circuit data isinserted therein and function verification has been performed, can avoidre-verification when the ASIC is formed. Further, this avoidsredesigning due to a difference between the ASIC and the programmablelogic device.

Further, the invention according to still another aspect of the presentinvention is a controller for a logic synthesis tool that controls thegeneration of a core (logic core) of a programmable logic deviceincluding ports of blocks formed of selected blocks and port connectioninformation, by selecting optional blocks constituting an ASIC from thecore (logic core) of the ASIC including ports of blocks and portconnection information, and grouping the selected blocks. The controllerincludes a unit that performs control for changing a net name given as aport name by the logic synthesis tool with respect to a port of the core(logic core) of the programmable logic device formed of blocks createdby the logic synthesis tool and selected by a designer, into a port nameof blocks constituting the connected programmable logic device bytracing the net connected to the port, a unit that creates a temporarychip design having the port designated by the chip terminal informationby the logic synthesis tool, a unit that generates the temporary chipdesign as a cell in the design, a unit that connects the temporary chipdesign with ports having the same name between cells, inserts an I/Obuffer depending on the device technology from the chip terminalinformation into the connected net, and replaces by a cell the core(logic core) of the programmable logic device formed of blocks createdby the logic synthesis tool and selected by the designer, whose name hasbeen changed, and a unit that creates a netlist of chips for theprogrammable logic device by expanding the top hierarchy of the core(logic core).

With such a configuration, the netlist of chips for the programmablelogic device can be created.

According to the present invention, a concurrent development method forconcurrent development of an ASIC and a programmable logic deviceincludes grouping/creating including grouping functional blocksconstituting the ASIC based on port connection information, and creatinga netlist, including ports of the functional blocks grouped and the portconnection information, as a core (logic core) of the programmable logicdevice, a logic synthesis data creating including creating logicsynthesis data for the ASIC and logic synthesis data for theprogrammable logic device from circuit data of the functional blocksconstituting the ASIC, a ROM data creating including creating ROM databy inserting the logic synthesis data for the programmable logic devicerelating to the functional blocks grouped, into the netlist created atthe grouping/creating, wherein the ROM data is used for evaluating realmachines in which a circuit of the programmable logic device isrecorded, performing ASIC layout creation and timing verificationconcurrently with the ROM data creating, using the logic synthesis datafor the ASIC created, and a difference reflecting including reflecting achange in the circuit data during the performing, based on a result ofevaluating the real machine using the ROM data created.

According to the present invention, a computer program for concurrentdevelopment of an ASIC and a programmable logic device, makes a computerexecute grouping/creating including grouping functional blocksconstituting the ASIC based on port connection information, and creatinga netlist, including ports of the functional blocks grouped and the portconnection information, as a core (logic core) of the programmable logicdevice, a logic synthesis data creating including creating logicsynthesis data for the ASIC and logic synthesis data for theprogrammable logic device from circuit data of the functional blocksconstituting the ASIC, a ROM data creating including creating ROM databy inserting the logic synthesis data for the programmable logic devicerelating to the functional blocks grouped, into the netlist created atthe grouping/creating, wherein the ROM data is used for evaluating realmachines in which a circuit of the programmable logic device isrecorded, performing ASIC layout creation and timing verificationconcurrently with the ROM data creating, using the logic synthesis datafor the ASIC created, and a difference reflecting including reflecting achange in the circuit data during the performing, based on a result ofevaluating the real machine using the ROM data created.

According to the present invention, the functional blocks constitutingthe ASIC are grouped based on the port connection information, and anetlist including the ports of the grouped functional blocks and theport connection information is created as a core (logic core) of theprogrammable logic device. The ASIC logic synthesis data and the logicsynthesis data for the programmable logic device are created from thecircuit data of the functional blocks constituting the ASIC. The logicsynthesis data for the programmable logic device relating to the groupedfunctional blocks is inserted in the created netlist to create ROM datafor evaluating the real machine in which the circuit of the programmablelogic device is recorded. Layout creation of the ASIC and the timingverification are performed concurrently with creation of the ROM datafor evaluating the real machine using the created logic synthesis datafor the ASIC. A change in the circuit data based on the evaluationresult of the real machine using the created ROM data is reflected increation of ASIC layout and timing verification. Consequently, efficientconcurrent development of the ASIC and the programmable logic devicebecomes efficient, thereby reducing the development period of the ASIC.

According to the present invention, a concurrent development system forconcurrent development of an ASIC and a programmable logic deviceincludes a netlist creating unit that creates a netlist, including portsof the functional blocks grouped and the port connection information, asa core (logic core) of the programmable logic device, by groupingfunctional blocks constituting the ASIC based on port connectioninformation, a logic synthesis data creating unit that creates logicsynthesis data for the ASIC and logic synthesis data for theprogrammable logic device from circuit data of the functional blocksconstituting the ASIC, a ROM data creating unit that creates ROM data byinserting the logic synthesis data for the programmable logic devicerelating to the functional blocks grouped, into the netlist created atthe grouping/creating, wherein the ROM data is used for evaluating realmachines in which a circuit of the programmable logic device isrecorded, and an ASIC layout creating unit that performs ASIC layoutcreation and timing verification concurrently with the ROM datacreating, using the logic synthesis data for the ASIC created.

According to the present invention, the functional blocks constitutingthe ASIC are grouped based on the port connection information, and anetlist including the ports of the grouped functional blocks and theport connection information is created as a core (logic core) of theprogrammable logic device. The ASIC logic synthesis data and the logicsynthesis data for the programmable logic device are created from thecircuit data of the functional blocks constituting the ASIC. The logicsynthesis data for the programmable logic device relating to the groupedfunctional blocks is inserted in the created netlist to create ROM datafor evaluating the real machine in which the circuit of the programmablelogic device is recorded. Layout creation of the ASIC and the timingverification are performed concurrently with creation of the ROM datafor evaluating the real machine using the created logic synthesis datafor the ASIC. Consequently, concurrent development of the ASIC and theprogrammable logic device becomes efficient, thereby reducing thedevelopment period of the ASIC.

According to the present invention, a concurrent development system forconcurrent development of an ASIC and a programmable logic device usedby a user from a computer connected to a network includes an ASIC logicsynthesis unit that executes logic synthesis of the ASIC in response toa request from the user, to obtain a first logic synthesis result, anASIC logic synthesis result determining unit that determines whether thefirst logic synthesis result satisfies a speed performance required bythe user, to obtain a determination result, a programmable logic devicelogic synthesis unit that executes logic synthesis of the programmablelogic device, based on the determination result to obtain a second logicsynthesis result, a logic synthesis result displaying unit that displaysthe first logic synthesis result and the second logic synthesis resulton the computer, and a logic synthesis informing unit that informs theuser by an e-mail, of start of the logic synthesis of the ASIC and thefirst logic synthesis result, and of start of the logic synthesis of theprogrammable logic device and the second logic synthesis result.

According to the present invention, a concurrent development method forconcurrent development of an ASIC and a programmable logic device usedby a user from a computer connected to a network includes a firstexecuting including executing logic synthesis of the ASIC in response toa request from the user, to obtain a first logic synthesis result,determining whether the first logic synthesis result satisfies a speedperformance required by the user, to obtain a determination result, asecond executing including executing logic synthesis of the programmablelogic device, based on the determination result to obtain a second logicsynthesis result, displaying the first logic synthesis result and thesecond logic synthesis result on the computer, and informing the user byan e-mail, of start of the first executing and the first logic synthesisresult, and of start of the second executing and the second logicsynthesis result.

According to the present invention, logic synthesis of the ASIC isexecuted in response to a user's request, it is determined whether thelogic synthesis result of the formed ASIC satisfies the speedperformance requested by the user. Logic synthesis of the programmablelogic device is executed based on the determination result. Theexecution result of logic synthesis of the ASIC and the execution resultof logic synthesis of the programmable logic device are displayed on acomputer, and an e-mail informing execution start and execution resultof logic synthesis of the ASIC, and execution start and execution resultof logic synthesis of the programmable logic device is sent to the user.Consequently, the user can execute logic synthesis at any time withoutproviding an exclusive operator for the logic synthesis, can maintainuniform logic synthesis quality as if the logic synthesis is performedby the exclusive operator, and can receive information of start andresult of the logic synthesis by the e-mail, thereby eliminating thenecessity of regularly confirming the progress of logic synthesis by acomputer.

According to the present invention, the concurrent development systemfor concurrent development of an ASIC and a programmable logic deviceaccording to the invention, further includes a netlist creating unitthat creates a netlist including port connection information of aplurality of functional blocks specified by the user, from functionalblocks constituting the ASIC, in response to a request of the user, aROM data creating unit that creates ROM data, in which a circuit of theprogrammable logic device is recorded, by inserting the data of thelogic synthesized target functional block into the netlist created bythe netlist creating unit, a ROM data creation result display unit thatdisplays a result of the creation of the ROM data, on the computer, anda ROM data creation result informing unit that informs the user by ane-mail, of the result of creation of the ROM data.

According to the present invention, a netlist including the portconnection information of a plurality of functional blocks specified bya user from the functional blocks constituting the ASIC is created inresponse to a user's request. ROM data in which a programmable logicdevice circuit is recorded is generated by inserting data of the logicsynthesized functional block in the created netlist, and the generationresult of the generated ROM data is displayed on a computer, andinformed to the user by an e-mail. Consequently, the user can save load,time and cost required for generating the ROM data in which theprogrammable logic device circuit is recorded, without providing adevelopment environment exclusively for the programmable logic device.

According to the present invention, the concurrent development systemfor concurrent development of an ASIC and a programmable logic deviceaccording to the above aspect, further includes a temporary netlistcreating unit that creates a netlist in which a dummy circuit isinserted in an input terminal and an output terminal of the functionalblock constituting the ASIC specified by the user, when designing of thefunctional block has not been completed, and when there is no circuitdata.

According to the present invention, when designing of the functionalblock constituting the ASIC specified by a user has not yet beencompleted and there is no circuit data, a netlist with a circuit inwhich a temporary flip-flop or the like is used for the input and outputterminals of the functional block inserted therein is created.Consequently, in the verification by prototyping of the programmablelogic device, even if designing of the functional block, which is not atarget of verification, has not yet been completed, verification byprototyping can proceed, thereby improving the efficiency ofverification.

According to the present invention, the concurrent development systemfor concurrent development of an ASIC and a programmable logic deviceaccording to the present invention, further includes a monitoring unitthat monitors the latest circuit data the user has and the scale ofchange in the circuit data incorporated in an implementation design byan implementation designer, to thereby obtain a monitoring result, achange timing informing unit that informs the user and theimplementation designer of the ASIC by an e-mail that it is time toreflect the change monitored, based on the monitoring result and thetime required for the layout designing, at a scheduled date and time,and a reflection suspension requesting unit using which the userrequests suspension of reflecting the change monitored, by altering thedate for reflecting the change monitored, in response to the e-mail.

According to the present invention, when the scale of change between thelatest circuit data held by the user and the circuit data incorporatedinto the implementation designing by the implementation designer ismonitored, and approaches the planned date based on the monitoringresult and the time required for layout design, the user and the ASICimplementation designer are informed by an e-mail of the change and thatit is time for reflecting the change in the ASIC implementation design.In response to this information, the user requests suspension, bychanging the date for reflection. Thus, the generated change isreflected efficiently in layout designing of the ASIC. By setting thetiming for reflecting the change, the user can determine until when thechange can be made, and can review the schedule at an early stage.

According to the present invention, a method of creating a netlist foran FPGA and an ASIC, includes, on the one hand, creating FPGA designinformation in which identical terminals in a first design and a seconddesign are connected, and a buffer corresponding to the FPGA is insertedbetween the terminals, from the first design and the second design,wherein terminal information of the FPGA including whole or a part offunctional blocks of a plurality of functional blocks is described inthe first design, and the terminal information identical to that of theFPGA described as a low-order layer of the first design is described inthe second design, and on the other hand, creating ASIC designinformation in which identical terminals in a third design and a fourthdesign are connected, and a buffer corresponding to the ASIC is insertedbetween the terminals, from the third design and the fourth design,wherein terminal information of the ASIC including the functional blocksis described in the third design, and the terminal information identicalto that of the ASIC described as a low-order layer of the third designis described in the fourth design, and replacing the second design bythe FPGA design information created and the fourth design by the ASICdesign information created, based on the connection information of thefunctional blocks included in each design.

Further, according to the present invention, to create a netlist for theFPGA and the ASIC, on the one hand, FPGA design information is createdin which the same terminals in a first design and a second design areconnected, and a buffer corresponding to the FPGA is inserted betweenthe terminals, from the first design in which terminal information ofthe FPGA including the whole or a part of functional blocks of aplurality of functional blocks is described, and the second design inwhich the same terminal information as that of the FPGA described as alow-order layer of the first design is described, and on the other hand,ASIC design information is created in which the same terminals in athird design and a fourth design are connected, and a buffercorresponding to the ASIC is inserted between the terminals, from thethird design in which terminal information of the ASIC including thefunctional blocks is described, and the fourth design in which the sameterminal information as that of the ASIC described as a low-order layerof the third design is described. This is followed by replacing each ofthe second design and the fourth design by the circuit informationcreated based on the connection information of the functional blocksincluded in each design. Consequently, efficient concurrent developmentof the ASIC and the programmable logic device becomes possible, therebyreducing the development period of the ASIC.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a flowchart of the principle of a method of the presentinvention;

FIG. 2 is a diagram for explaining the operation of a first embodimentof the present invention;

FIG. 3 is a block diagram of one embodiment of a logic synthesis toolcontroller of the present invention;

FIG. 4 is a block diagram of one embodiment of the controller;

FIG. 5 is a flowchart (1) of a core (logic core) generator program;

FIG. 6 is a flowchart (2) of the core (logic core) generator program;

FIG. 7 is a flowchart of the detailed procedure in the first embodimentof the present invention;

FIG. 8 is a flowchart of core (logic core) design check control;

FIG. 9 is a flowchart of grouping control;

FIG. 10 is a flowchart for controlling the insertion of an I/O bufferand an image in the process;

FIG. 11 is a flowchart of a procedure for designing integrated circuits;

FIG. 12 is a diagram for explaining the concept of concurrentdevelopment of an ASIC and an FPGA according to a second embodiment;

FIG. 13 is a functional block diagram of a system configuration of aconcurrent development system of the ASIC and the FPGA according to thesecond embodiment;

FIG. 14 is one example of a directory configuration for storing data ina file server;

FIG. 15 is one example of a logic CORE generation table;

FIG. 16 is a flowchart of a process procedure of the concurrentdevelopment system of the ASIC and the FPGA in the second embodiment;

FIG. 17 is one example of a login screen;

FIG. 18 is one example of a procedure screen;

FIG. 19 is a flowchart of a process procedure for a logic COREgenerating interface program;

FIG. 20 is one example of a logic CORE generating interface screen;

FIG. 21 is a flowchart (1) of a process procedure for an ASIC logic COREgenerator program;

FIG. 22 is a flowchart (2) of a processing procedure for the ASIC logicCORE generator program;

FIG. 23 is a flowchart of a process procedure for a logic core checkprogram;

FIG. 24 is one example of a status display selection screen;

FIG. 25 is one example of a logic CORE generating status screen;

FIG. 26 is a flowchart of a process procedure on the logic coregenerating status screen of the ASIC;

FIG. 27 is one example of an FPGA logic CORE generating interfacescreen;

FIG. 28 is a flowchart (1) of a processing procedure for an FPGA logicCORE generator program;

FIG. 29 is a flowchart (2) of a processing procedure for the FPGA logicCORE generator program;

FIG. 30 is one example of a compatible package table;

FIG. 31 is a flowchart of a process procedure for a logic synthesisinterface program;

FIG. 32 is one example of a logic synthesis interface screen;

FIG. 33 is a flowchart of an FPGA logic synthesis interface processprocedure;

FIG. 34 is one example of a logic synthesis status screen;

FIG. 35 is one example of an input and execution screen of fitting data;

FIG. 36 is one example of a ROM data generating status screen;

FIG. 37 is one example of a schedule and result screen; and

FIG. 38 is one example of a operation time setting file.

BEST MODE FOR CARRYING OUT THE INVENTION

Exemplary embodiments of the present invention will be explained indetail with reference to the accompanying drawings.

FIG. 2 is a diagram for explaining the operation of the first embodimentof the present invention. An integrated circuit is developed based onshared design data and based on the study of the circuit architecture.

When designing a function to be realized using the HDL, a chip, being aproduct itself, is formed of an instance having a certain function. Theinstance refers to a block with a plurality of functions designed by theHDL, and multiple blocks if a specific block is necessary for realizinga function of the chip.

In FIG. 2, X, Y, and Z are tables in which a port specification of ablock created after studying the circuit architecture is definedaccording to a defined format. These tables X, Y, and Z are alwayscreated when a block is designed, and include block name, instance name,port name, range, input/output, type, instance name on output side,output port name of the instance on the output side, and the like. Thesedata are input manually by a user. It is the key point of the presentinvention to create the respective tables beforehand.

S1 is a step of generating a core (logic core) including only ports ofblocks and connection information between the blocks, the step beingexecuted by a unit that checks whether connection between instances andbetween an instance and an external terminal defined as a terminal ofthe instance and a terminal of a device package are realized withoutcontradiction, and a unit that defines a net between the instances. Ifthere is an error at step S1, the error is fed back to the user and theuser re-inputs data (circular arrow 1 in the figure denotes repetition).

S2 is a step of referring to an FPGA table 2, reading the core (logiccore) output at step S1 into a logic synthesis tool, selecting a groupof instances forming a programmable logic device by controlling thefunction of the logic synthesis tool, generating a new core (logic core)in a state with hierarchical information being preserved, and outputtinga netlist of a core (logic core) same as the core (logic core) output atstep S1, and that does not include an I/O buffer and the like dependingon the device technology.

S3 is a step of generating a temporary core (logic core) from a terminalname in terminal specification table data of a device package in adefined format, inserting the I/O buffer depending on the devicetechnology specified by the table data into a port of the temporary core(logic core), and replacing the temporary core by the netlist output atstep S2, which is the key point of the present invention. After creatingthe netlist of chips for a target device by this process, logicsynthesized circuit data is read from an FPGA synthesis result library3, based on the target device technology, by controlling the function ofthe logic synthesis tool, and inserting the read circuit data into thecorresponding block, thereby completing the netlist for a desireddevice. The netlist generated as the FPGA is fitted by an FPGA layouttool to form ROM data.

An ASIC is formed by referring to an ASIC synthesis result library 4 atstep S2.

According to the first embodiment, in the development of integratedcircuits, the quality of a port specification of a block, being an inputin RTL designing, is ensured beforehand. Further, even in thedevelopment of large scale integrated circuits in which there are manyfunctional blocks and many design resources, since the connectionbetween the blocks can be confirmed beforehand, it can be ensured thatthe chip is assembled without fail.

FIG. 3 is a block diagram of one embodiment of a logic synthesis toolcontroller of the present invention. A controller 22 controls theoverall operation, a CRT 24 displays various kinds of information, aninput unit 21 inputs various kinds of commands and the like to thecontroller 22, and a storage unit 23 stores various kinds ofinformation, and is connected to the controller 22.

The input unit 21 inputs a core (logic core) generator program startcommand and a logic synthesis tool control command, and the logicsynthesis tool, the core (logic core) generator program, and the logicsynthesis control program are stored in the storage unit 23.

When a table file of the block is specified by the input unit 21 toinput the core (logic core) generator program start command, the core(logic core) generator program reads the table file to generate a core(logic core), and outputs the file to the storage unit 23. If an erroroccurs during the process, error information is displayed on the CRT 24.

If there is an error, the designer corrects the table file and executesthe command again. To control the logic synthesis tool, necessary datais first prepared as a file and stored in a predetermined location inthe storage unit 23 together with the core (logic core) file generatedby the core (logic core) generator program. When the input unit 21inputs the logic synthesis tool control command, the logic synthesistool is executed and the process result is displayed on the CRT 24. Ifthe process fails, the state at the time of failure is displayed on theCRT 24.

FIG. 4 is a block diagram of one embodiment of the controller 22 shownin FIG. 3. Like parts in FIG. 3 are designated by like reference signs.In FIG. 4, a CPU 31 controls the whole operation, a memory 32 storesvarious kinds of information, a keyboard 21 inputs various commands andthe like, and a CRT 24 is a display unit. A storage unit 23 includes acore (logic core) generator program 36, a logic synthesis tool controlprogram 35, a logic synthesis tool 34, and an operating system (OS) 33.A bus 37 interconnects respective components. The storage unit 23 may bea hard disk drive.

In the system formed in this manner, when a command from the keyboard 21is input to the CPU 31, the CPU 31 searches the storage unit 23 for therelevant program, and executes the relevant program.

FIGS. 5 and 6 are flowcharts of the core (logic core) generator program.Table data in X, Y, and Z in FIG. 2 will be used for explanation. Thefiles in the table data X, Y, and Z (instances are also X, Y, and Z) areread, and processing is performed for each file one by one. The data inX is read at step F1, and the whole data in the table of port A isextracted and stored in the memory at step F2. The subsequent process isperformed by referring to the data in the memory. Next, it is checkedwhether the port is for an output, at step F2′.

Because the port A is for input, control proceeds to step F3′. At stepF3′, it is checked whether there is a connection keyword with a packageterminal. Because there is no connection keyword with the packageterminal, step F4 of storing the package terminal information in thememory is skipped. Next, at step F2, the whole data of the next port Bis stored in the memory.

Because the port B is for output, “XB” is output to the file A in thestorage unit 23 at step F3. Here, X is a file name and B is a port name.Because there is no connection keyword with the package terminal, stepF4 is skipped. Next, at step F2, the whole data of the next port Z isstored in the memory. Because the port Z is for output, “XZ[2:0]” isoutput to the file A at step F3. Here, [2:0] indicates 2, 1, 0.

Because there is no connection keyword with the package terminal, stepF4 is skipped. Next, at step F2, the whole data of the next port I isstored in the memory. Because the port I is for input, step F3 isskipped. Because there is the connection keyword “IO” with the packageterminal, “INPUT, in, 2:0” is stored as a port name of the core (logiccore) in the memory. Next, it is checked whether the process for allports has finished (F4′). If the process for all ports has not finishedyet, control returns to step F2.

The processing for all ports in X is complete, and in the case of VHDL,an entity file having the following information is output to the storageunit 23.

A: in std_logic;

B: out std_logic;

Z: out std_logic vector (2 down to 0); and

I: in std_logic.

The above process is also performed for data of Y and Z. When theprocess has finished for the whole file (F5′), and if it is VHDL at stepF6, the entity file of the core (logic core) having the followinginformation is output to the storage unit 23.

INPUT: in std_logic;

OUT: out std_logic;

The following data is stored in the file A.

XB, XZ [2:0], YC [1:0], YO, ZF

The data in the file A is read at step F7, stored in the memory at stepF8, and the process is performed for the files one by one. At step F8′,it is checked whether the port is for input. The table data in X will beexplained here as an example. Because the port A is for input, at stepF9, Y of the output side and C of the port name are extracted. At stepF10, YC [1:0] is searched in the data stored at step F8. It is thenchecked if these match with each other at step F10′.

Because YC [1:0] is found in the search, connection information as shownbelow is output to a file B at step F12. If the result does not matchtherewith, error information indicating that the port name or the rangeis different is output to a log file in the storage unit 23, and is alsodisplayed on the CRT 24.

A=>YC

Next, because the port B is for output, the following connectioninformation is output to the file B at step F11.

B=>XB

Next, because the port Z is for output, the following connectioninformation is output to the file B at step F11.

Z=>XZ

Next, the port I is for input, but “IOINPUT” cannot be found by thesearch at step F10. Therefore, at step F13, this matter is output to thelog file as an error, and displayed on the CRT 24. However, in the caseof a port connected to a terminal of the package, there is no problem.On the contrary, it can be confirmed which port in which instance isconnected to which terminal of the package, from the error informationoutput to the log file. Next, at step F12, the following connectioninformation is output to File B.

I=>IOINPUT

At step F12′, it is checked whether the process for all ports in alltables has finished, and if not, control return to step F8′.

The above processing is also performed for the table data in Y and Z,and when the processing has finished, a port for which the connectioninformation cannot be formed is output to the log file at step F14. Atstep F15, the entity list of the core (logic core) output at step F6 iscombined with the connection information output at steps F11 and F12, tocreate a netlist of the core (logic core), and the netlist is output tothe storage unit 23.

FIG. 7 is a flowchart of the detailed procedure in the first embodimentof the present invention. This flowchart depicts in detail, theprocessing at S2 onward, in which the core (logic core) output at S1 isinput (see FIG. 2). In FIG. 7, a solid line indicates the flow of theprocess, and a broken line indicates the flow of the data.

A core (logic core) design is first checked (step a1). It is thenchecked whether the core (logic core) design is OK (step a1′). If thecore design is not OK, the table data in FIG. 2 is checked and theprocessing is executed again (step a10). If the core design is OK, thefiles 12 and 13 are referred to, grouped (step a2), and stored as thecore (logic core) 10. A dummy core (logic core) 11, including theterminal name and the buffer name, is generated by referring to thetable 14 (step a3).

The I/O buffer is inserted therein based on the dummy core (logic core)11 and the table 14 (step a4). The core (logic core) 10 and the dummycore (logic core) 11 are checked by comparison (step a5). It is thenchecked whether the core (logic core) is OK (step a5′). As a result ofcomparison, if the core (logic core) is OK, termination processing isperformed (step a6). If it is not OK, the terminal specification of thedevice package is checked (step a9), the table data in FIG. 2 ischecked, and the processing is re-executed.

After the termination processing at step a6, the circuit data isinserted by referring to a synthesis result file 15 (step a7), and a DFTcircuit is inserted by referring to a file 16 (step a8).

Next, the various steps explained in FIG. 7 will be explained in furtherdetail. FIG. 8 is a flowchart of core (logic core) design check control.At first, it is checked whether a file of the core (logic core) ispresent (step all), and if the file is present, the logic synthesis toolreads the file (step a12). If not, nothing is done. At step a1 (see FIG.7), the core (logic core) output at step S2 of FIG. 2 is input. At thestep of checking the HDL descriptive grammar of the core (logic core)and an unused input port and the like, if the file of the core (logiccore) is present, then at step a12, the core (logic core) is read by thelogic synthesis tool. The logic synthesis tool has a function ofchecking the grammar and the like at the time of reading the file, andin case of an error, the content is confirmed from the CRT, the tabledata describing the port specification of the block is reviewed, and thedesign check is executed again, as shown at step a10.

FIG. 9 is a flowchart of the grouping control, and includes the detailsof step a2 of FIG. 7. At first, it is checked whether a file of the core(logic core) is present (step a13). If the file is present, it ischecked whether a file of instances to be grouped is present (step a14).When there is the file, that is, when there is no problem in the resultat step a1. If there is a file 13 in which the block name to be formedinto the programmable logic device is written, one block per line, thefile 13 is read (step a21), and grouped as a new core (logic core) bycontrolling the grouping function of the logic synthesis tool, in astate such that the hierarchy information of the target block ismaintained (step a22).

When the grouping function is used, because the port name of the core(logic core) becomes the net name for connecting the instances, the netis traced into the core (logic core) with respect to all ports of thecore (logic core), a new port is generated in the core (logic core) in aport name of the first instance found, and connected to a new port thathas generated a net connected to the port of the core (logic core),having the name of the net, and the port having the net name is deleted(step a23). This for creating a new port and deleting an old port.

It is then checked whether there is monitor port information (stepa23′). If there is monitor port information, a port is generated in thecore (logic core) in a port name of a specified instance, and connectedto a terminal of the block (step a24). If there is no monitor portinformation, a netlist that does not include an I/O buffer or the likedepending on the device technology is output to the storage unit 10 (seeFIG. 7) (step a25). In such a case, this can be confirmed on the displayunit, by using the display function of the logic synthesis tool.

At step a2 of FIG. 7, if necessary, the port of the grouped blocks canbe generated as a port of the core (logic core) (step a24). Thisfunction is used when there is a port to be monitored at the time ofevaluating the function of the programmable logic device. The specifyingmethod is executed, by performing grouping, changing the port name, andthen reading the file in which one port name is written per line, asshown in file 12.

Up to this step, there should be no error in the port connection betweenblocks in the core (logic core), because the designer himself generatesthe core (logic core) by using the data for determining the portspecification of the block. However, in the case of the ASIC in whichthe core (logic core) generated at step S1 (see FIG. 2) is directlyused, generally the terminal name of the device package to be defined inthe table data of the block within the core (logic core) is determinedby referring to the terminal specification of the device package, and assuch, there may be a difference due to a simple mistake or a change fromthe print substrate design. In contrast, when the port of the core(logic core) generated at step a2 (see FIG. 7) becomes the terminal ofthe device package, because the port specifies the specification, theremay be a difference as well. This problem is solved by steps a3 to a5.

FIG. 10 is a flowchart for controlling the insertion of the I/O bufferand an image in the process. This flowchart depicts the process at stepa4 in FIG. 7. In the explanation below, steps from a3 to a5 areseparate, but actually, the process is a series of processes within onecommand.

At first, it is checked whether there is a file with external terminalinformation and the core (logic core) (step a15). If there is such afile, the following processing is performed. At step a3, different fromstep a2, as shown in 14 in FIG. 7, if there is table data of terminalspecification of the device package in which a terminal name is definedin the first column, and the I/O buffer name depending on the devicetechnology to be used is defined in the second column, the table data isread to create a dummy chip design (a first design describing theterminal information with the name written in the first column) (stepa31). The dummy chip design is generated as a cell (a second designdescribing the terminal information identical to the first design,described as a low-order layer of the first design), the design isconnected to a port having the same name as that of the cell, and adummy core (logic core) is output to the storage unit 11.

At step a4, the dummy core (logic core) in the storage unit 11 is read,and the I/O buffer depending on the device technology, written in thesecond column in the terminal specification table data 14 of the devicepackage, is inserted from the chip terminal information into the net ofthe dummy core (logic core).

At step a5, from among the ports of the dummy core (logic core), a portfor testing a specific device not related to the logic that is notrelated to functions, is deleted, the dummy core (logic core) isreplaced by the core (logic core) in the storage unit 10 as a celltherein (step a33), and it is checked whether there is unmatching in theterminal name (step a33′). If the corresponding port names of the twocores (logic cores) match with each other, insertion is successful. Inthis manner, the terminal name in the terminal specification table dataof the device package, and the port name of the core (logic core) can becrosschecked, thereby solving the above problem. If there is unmatching,the processing ends, and if there the names match, the netlist isoutput.

If the insertion fails, as shown in step a9 of FIG. 7, the terminalspecification of the device package is checked, and the control returnsto step a3. Alternatively, control returns to step a10, where the tabledata defining the terminal specification of the block is checked, andstep S1 onward are repeated (see FIG. 2). If the insertion issuccessful, the hierarchy of the core (logic core) is expanded to form achip.

At step a6, a flip-flop is connected to the input/output ports of allblocks of the chip, and termination processing is performed. Thistermination processing is for creating an error-free netlist, even ifthere is a block in which the circuit design is not complete, therebyenabling the layout work.

At step a7, the logic synthesized circuit data is read from a synthesisresult library and inserted in a corresponding block. At this time, ifthere is no synthesis result with respect to a block in the chip, andthe design name or cell name of the block conforms to the naming rule,the input port and the output port of the block are connected within theblock according to a predefined rule.

This process is executed when there is no synthesis result in the caseof the programmable logic device, and a specific block such as DLL ofthe programmable logic device is changed into an ASIC. By the processfor connection within the block without deleting the block, thearchitecture can be maintained. Further, when there is a macro such as amemory in the block, the macro is replaced by circuit data of adevice-specific memory.

Step a8 is a process performed in the case of the ASIC. A SCAN testcircuit for testing the device is automatically inserted, or a file 16defining the order of blocks connected to the SCAN test circuit isinput, and connection is performed according to the defined order.

According to the first embodiment, the core (logic core) is generatedfrom the data from the design document, and a new core (logic core) isgenerated for the programmable logic device from the core (logic core),in the state with the hierarchy structure and the connection informationbeing preserved. Consequently, the circuit architecture can be shared,and the circuit data and the net between the instances that do notdepend on the device technology within the instance in which theinsertion function of the circuit data in the core (logic core) has beenverified can avoid re-verification when the ASIC is formed. Thus, theconcurrent development of the ASIC and the programmable logic device canbe performed efficiently.

The concurrent development of the ASIC and the FPGA according to thepresent invention will be explained in detail as a second embodiment.There are various logic design languages such as C language, UML, andthe like, but in the second embodiment, HDL is exemplified as the designlanguage.

At first, the concept of the concurrent development of the ASIC and theFPGA according to the second embodiment will be explained with referenceto FIG. 12. The characteristic of the concurrent development of the ASICand the FPGA is that in order to execute prototyping verification by theFPGA concurrently with the implementation designing of the ASIC, ROMdata in which an FPGA circuit required for the prototyping verificationis recorded, is provided by the implementation design of the ASIC, sothat the development of the ASIC and the FPGA can be made seamless.

In the concurrent development of the ASIC and the FPGA, the prototypingverification by the FPGA is taken into consideration during the study ofcircuit architecture, division of functions to be realized in a circuitto be realized having a suitable expected size and hierarchization offunctions due to structural difference between the ASIC and the FPGA iscarried out, to thereby create a common functional block configurationbetween the ASIC and FPGA designs, and a port specification of thefunctional block. The data of the functional block configuration and theport specification data of the functional block becomes data common tothe floor plan for ASIC implementation designing, logic synthesis, andlayout designing.

In RTL designing and verification, RTL designing common to the ASIC andthe FPGA is performed according to the structure obtained after studyingthe circuit architecture, and software verification is performed using alogic verification tool, with emphasis on a corner case for eachfunction. The logic synthesis of the ASIC is executed concurrently withthe RTL designing and verification, and after the characteristics as theASIC can be ensured, logic synthesis of the FPGA is executed, to form acircuit in the FPGA on a substrate for prototyping sequentially, therebyenabling verification by the FPGA prototyping.

On the other hand, in the ASIC layout, software verification and theverification result by prototyping are reflected concurrently at anytime, based on the common functional block configuration between theASIC and FPGA designs, thereby shortening the period from the completionof verification by the FPGA prototyping to the completion of developmentof the ASIC.

The system configuration of the concurrent development system of theASIC and the FPGA according to the second embodiment will be explainednext, with reference to FIG. 13. The concurrent development system 200of the ASIC and the FPGA includes a firewall 210, a Web server 220, auser authentication server 230, a user management server 240, a logicsynthesis server 250, a mail server 260, a file server 270, anapplication server 280, and a monitoring server 290. The concurrentdevelopment system 200 of the ASIC and the FPGA can be used via theInternet from a Web client 100.

The firewall 210 is a computer that accepts only an access requestaccording to a preset communication procedure from among access requeststhrough the Internet, to prevent illegal access from the outside to theconcurrent development system 200 of the ASIC and the FPGA.

The Web server 220 performs information transmission in response to arequest from the Web client 100 made through the Internet. The Webserver 200 includes a logic CORE generating interface program 221 thatgenerates a logic CORE only from ports of functional blocks constitutingthe ASIC or the FPGA and the port connection information of thefunctional blocks, a logic synthesis interface program 222, a fittinginterface program 223, a status display interface program 224, a formatfile required for generating the logic CORE, and a format file requiredfor logic synthesis. The computer executes these programs in response toa request from the Web client 100, and transmits the result to the Webclient 100.

The user authentication server 230 performs authentication of users, anduser names and passwords to be used are registered therein based on thematching. The user management server 240 registers and deletes users,and user names, project names, and e-mail addresses to be used areregistered therein based on the matching.

The logic synthesis server 250 includes an ASIC logic CORE generatorprogram 251, an FPGA logic CORE generator program 252, an ASIC logicsynthesis program 253, an FPGA logic synthesis program 254, and afitting program 255 that is a layout of the FPGA. The logic synthesisprograms and the fitting program in the logic synthesis server 250 areactivated from the logic synthesis interface program 222, and are meantto read an RTL source stored in the file server 270 and to execute logicsynthesis of the ASIC and the FPGA and fitting of the FPGA.

The mail server 260 includes mail transfer software, and distributes theprocessing information of the process executed by the Web server 220 andthe information from the Web client 100 to the user and the system, bye-mail.

The file server 270 stores the RTL source to be logic synthesized, thelogic synthesis results, and ROM data of the FPGA. FIG. 14 is oneexample of a directory configuration for storing data in the fileserver. Project 41 is a directory of project names for developing theASIC and the FPGA, or nicknames of the ASIC, and the name is set basedon the matching.

IO 42 is a directory that stores data for generating the logic CORE, andincludes, for each functional block constituting the ASIC, a directoryASIC 48 that stores a file of tables for generating the logic COREdescribing the port specification of the functional blocks shown in FIG.15, and a directory FPGA 49 that stores the file of tables forgenerating the logic CORE in the directory ASIC 48 copied by the logicCORE generating interface program 221 according to a designation of auser. Further, under the directory FPGA 49, there are a number ofdirectories equal to the number of the FPGAs set by the user. Thedetails of the table for generating the logic CORE and the logic COREgenerating interface program 221 will be described later.

CORE 43 is a directory that stores the logic CORE generated by the logicCORE generator program, and includes a directory ASIC 50 for storing thelogic CORE of the ASIC generated from the port specification of thefunctional blocks constituting the ASIC, and a directory FPGA 51 forstoring the logic CORE of the FPGA from the port specification of thefunctional blocks constituting the FPGA.

RTL 44 is a directory that stores circuit design data (hereinafter,“RTL”) expressed in the HDL uploaded by the user from the logicsynthesis interface (described later), and includes a directory ASIC 52for storing the RTL in a unit of functional block constituting the logicCORE of the ASIC, and a directory FPGA 53 for copying the RTL in theASIC directory according to a designation of the user and storing theRTL.

SYNTHESIS 45 is a directory that stores the result of logic synthesis ofthe RTL performed by the logic synthesis server 250, and includes adirectory ASIC 54 that further includes a directory for storing thelogic synthesis results of the ASIC for each functional blockconstituting the ASIC logic CORE, and a directory FPGA 55 having adirectory for storing the logic synthesis results of the correspondingFPGA.

ROM 46 is a directory for storing the ROM data that stores the FPGAcircuit data generated after fitting that is the FPGA layout, based onthe logic synthesis results of the FPGA, and includes a directory forstoring each FPGA. LAYOUT 47 is a work directory using which a layoutdesigner of the ASIC performs layout designing of the ASIC.

The application server 280 (see FIG. 13) includes an ASIC floor planprogram, an ASIC layout design program, and an ASIC timing verificationprogram. An implementation designer uses this computer to execute thefloor plan, the layout designing, and timing verification of the ASIC.

The monitoring server 290 obtains a user name and a project nameregistered in the user management server 240, to compare the data in thedirectory LAYOUT 47 managed by the implementation designer and the datain other directories, to perform logic synthesis, and to collect timerequired by the tool for the layout processing, in the data in thedirectories of the respective project names, twice, once in one day. Atthe first time, contents of the changes are informed to theimplementation designer, and at the second time, the schedule reflectingthe change is updated based on the collected time.

The process procedure of the concurrent development system 200 of theASIC and the FPGA in the second embodiment will be explained withreference to the flowchart in FIG. 16.

When the Web client Web client 100 accesses the concurrent developmentsystem 200 of the ASIC and the FPGA, the Web server 220 sends thedisplay control data for the login screen shown in FIG. 17 to the Webclient 100, and the Web client 100 displays the screen based on thereceived data. When the user inputs the user name and the passwordregistered on the login screen based on the matching and presses a loginbutton, the Web client 100 sends the user name and the password to theWeb server 220.

The Web server 220 refers the received user name and password to theuser authentication server 230. The user authentication server 230confirms whether the user name and the password are registered (stepS501), and returns the result to the Web server 220. When rejected bythe user authentication server 230, the Web server 220 sends the displaycontrol data for a login rejection screen to the Web client 100, and theWeb client 100 displays the login rejection on the screen based on thereceived data and finishes the processing (step S502).

If the user authentication server 230 accepts the user name and thepassword, the Web server 220 sends the display control data for aprocedure screen shown in FIG. 18 to the Web client 100, and the Webclient 100 displays the procedure screen based on the received data(step S503).

The user selects a menu from the procedure screen shown in FIG. 18, toperform concurrent development of the ASIC and the FPGA. If the userselects “format 1” and “format 2” (Yes at step S504), a format filerequired for the target design is downloaded from the Web server 220 tothe Web client 100 (step S505).

The “format 1” is format data of the table for generating the logicCORE, as shown in FIG. 15. The “format 2” is format data of a tabledefining terminal names and terminal number assignment for the ASICpackage used in the logic synthesis of the ASIC, and the I/O buffer forelectrically interfacing between the ASIC and external devices.

If the user selects logic CORE generation (Yes at step S506), the Webclient 100 sends information indicating that logic CORE generation hasbeen selected to the Web server 220, and the Web server 220 activatesthe logic CORE generating interface program 221 (step S507).

If the user selects logic synthesis (Yes at step S508), the Web client100 sends information indicating that logic synthesis has been selected,and the Web server 220 activates the logic synthesis interface program222 (step S509).

If the user selects fitting (Yes at step S510), the Web client 100 sendsinformation indicating that fitting has been selected to the Web server220, and the Web server 220 activates the fitting interface program 223(step S511).

If the user selects status display (Yes at step S512), the Web client100 sends data to the Web server 220 informing that the status displayhas been selected, and the Web server 220 activates the status displayinterface program 224 (step S513).

A process procedure for the logic CORE generating interface program 221will be explained next with reference to the flowchart in FIG. 19. Thelogic CORE generating interface program 221 sends the display controldata for the logic CORE generating interface screen shown in FIG. 20 tothe Web server 220. The Web server 220 sends the received displaycontrol data for the logic CORE generating interface screen to the Webclient 100. The Web client 100 displays the logic CORE generatinginterface screen based on the received display control data for thelogic CORE generating interface screen (step S801).

The user inputs a project name and presses “execute” button, to therebyspecify a file of the logic CORE generation table shown in FIG. 15, inwhich the IO specification of the functional block constituting the ASICfor generating the ASIC logic CORE is defined, based on a file selectionscreen displayed by the Web client 100.

The Web client 100 sends the project specification data and the file ofthe IO logic CORE generation table to the Web server 220. The Web server220 creates directories such as IO 42, CORE 43, RTL 44, SYNTHESIS 45,ROM 46, and LAYOUT 47 (shown in FIG. 14) in the file server 270 (stepS802), stores the files of the logic CORE generation table in thedirectory ASIC 48 under the IO 42, specifies the project name, executesthe ASIC logic CORE generator program 251, and stores an executionprocess ID in the memory (step S803).

The process procedure for the ASIC logic CORE generator program 251 isexplained next with reference to flowcharts in FIGS. 21 and 22. As shownin FIG. 21, the ASIC logic CORE generator program 251 reads the tablesX, Y, and Z for generating the logic CORE shown in FIG. 15 from thedirectory ASIC 48 shown in FIG. 14, to perform the process for each fileone by one.

The tables X, Y, and Z for generating the logic CORE define the portspecification of the functional block created based on the study of thecircuit architecture according to the defined “format 1”. These tablesare always created when designing the functional block, and includefunctional block name, instance name, port name, range, input/output,type, output side instance name, and output port name of the output sideinstance. The instance refers to the functional block constituting theASIC, and when a plurality of functional blocks having the same functionis used, the instance names thereof are changed and incorporated.

At first, X data is read (step S1001), the whole data in the table ofport A is extracted and stored in the memory (step S1002), to check ifthe port A is for output (step S1003). Because the port A is for input,it is checked if there is a connection keyword “IO” with the packageterminal (step S1005). Because there is no keyword “IO”, the whole dataof the port B is stored in the memory.

Because the port B is for output, “XB” is output in a file name A to thedirectory ASIC 50 in FIG. 14 (step S1004). Because there is noconnection keyword “IO” with the package terminal, the whole data of thenext port Z is stored in the memory. Because the port Z is for output,“XZ[2:0]” is output to the file A. Because there is no connectionkeyword “IO” with the package terminal, the whole data of the next portI is stored in the memory.

Since the port I is for input, and there is the connection keyword “IO”with the package terminal, “INPUT, in, 2:0” is stored in the memory asthe port name of the logic CORE (step S1006). The processing of allports in X is complete (Yes at step S1007), and the entity file definingthe port name, input/output, and range information is output to thedirectory ASIC 50 in FIG. 14, in a name of X, according to the grammarof the HDL (step S1008). In the case of VHDL, the contents to be outputare as follows:

A: in std_logic;

B: out std_logic;

Z: out std_logic_vector (2 down to 0);

I: in std_logic.

The above processing is also performed for the data in Y and Z. At thisstage, the following data is recorded in the file A.

XB, XZ[2:0], YC[1:0], YO, ZF

When the processing of all tables in the X, Y, and Z is complete (Yes atstep S1009), the data in the file A is read (step S1010), and stored inthe memory (step S1011). This processing is performed for each file oneby one. The table data in X will be explained here as an example. Atfirst, it is checked if the port A is for input (step S1012). Becausethe port A is for input, Y on the output side and C as the port name areextracted (step S1013). YC[1:0] is then searched in the memory (stepS1014), to check if there is matching data (step S1016). Because thematching data is found in the memory, the following connectioninformation is output in a file name B in the directory ASIC 50 (stepS1018).

A=>YC

When there is no matching data, error information indicating that theport name or the range is different is output to the log file in thedirectory ASIC 50 (step S1017).

Likewise, because the port B is for output, the following connectioninformation is output to the file B in the directory ASIC 50 (stepS1015).

B=>XB

Likewise, because the port Z is for output, the following connectioninformation is output to the file B in the directory ASIC 50.

Z=>XZ

Because the port I is for input, and “IOINPUT” cannot be found by thesearch, error information is output to the log file in the directoryASIC 50. However, in the case of the port connected to the packageterminal, it is not a problem, and on the contrary, it can be confirmedwhich port in which instance is connected to which terminal of thepackage from the error information output to the log file. The followingconnection information is then output to the file B in the directoryASIC 50.

I=>IOINPUT

When the above process has finished for the table data in Y and Z (Yesat step S1019), a port for which the connection information cannot becreated is output to the log file (step S1020), and in the case of VHDL,the entity file of the ASIC logic CORE having the following informationis output to the directory ASIC 50 (step S1021).

INPUT: in std_logic;

OUT: out std_logic;

Further, the entity file of the logic CORE and the connectioninformation are combined, and the ASIC logic CORE is output to thedirectory ASIC 50 in a file with a project name specified in FIG. 17 tofinish the process, and control returns to the logic CORE generatinginterface program 221 shown in FIG. 19 (step S1022).

The logic CORE generating interface program 221 checks if there is anerror in the log file in the directory ASIC 50. If an error is recorded(Yes at step S804), the error is read (step S805), the project name, thee-mail address of the user obtained by referring to the user managementserver 240 using the project name, the error information, and theprocess ID are sent to the mail server 260, and the mail server 260transmits an e-mail to the user (step S806). The user confirms the errorcontent by the e-mail, and repeats the processing for generating thelogic CORE until there is no error.

On the other hand, if an error has not been recorded in the log file (Noat step S804), the e-mail address of the user obtained by referring tothe user management server 240 using the project name, the process ID,and a logic CORE generation completion message are sent to the mailserver 260 (step S807), and the mail server 260 transmits an e-mail tothe user.

Further, a directory is created with the name of “CORE+process ID+dateand time” in the directory ASIC 50, the logic CORE created in theproject name in the directory ASIC 50 and the log file are shifted tothis directory, and a directory is created in this directory in the nameof IO. The table data in the directory ASIC 48 used for generating thelogic CORE is shifted to this IO directory, and the project name and thedirectory name of the logic CORE created in the name of “CORE+processID+date and time” are specified in a logic CORE check program in thelogic synthesis server 250, to activate the logic CORE check program(step S808).

In this logic CORE check program, commands of the logic synthesis toolare described so as to perform grammar check of the ASIC logic CORE, andnon-connection check of the input/output port of the respectiveinstances constituting the logic CORE, to output a report.

The process procedure for the logic CORE check program will be explainedbelow with reference to a flowchart in FIG. 23. This logic CORE checkprogram is under the received directory in the project name, wherein itis checked whether there is a directory of the target ASIC logic CORE inthe directory ASIC 50 shown in FIG. 14 (step S1201), and if Yes at stepS1201, a WORK directory is created in the ASIC directory including thelogic CORE directory (step S1202), so that the logic synthesis toolexecutes checking (step S1203).

When the execution has finished, the error information is extracted fromthe report file in the WORK directory, and sent to the mail server 260,together with the e-mail address of the user obtained by referring tothe user management server 240 using the project name and the process IDextracted from the logic CORE directory name, and the mail server 260transmits these by e-mail to the user (step S1204). The user confirmswhether the error information is an intended piece of information fromthe content of the transmitted e-mail.

The logic CORE generated in the series of flow ensures that the ASIC isassembled at all times, unless there is a connection error between theinstances constituting the ASIC in the user's logic design. This effectappears in the logic verification. When an operation different from theexpected operation is performed in the function verification of aplurality of instances constituting the ASIC, because connection betweenthe instances is ensured, it is possible to debugging with focus on therespective functions constituting the instance.

The process when the user selects status display on the procedure screenin FIG. 18 will be explained next. When the user selects status displayon the procedure screen in FIG. 18, the status display interface program224 is activated. The display control data for the status displayselection screen shown in FIG. 24 is transmitted to the Web server 220.The Web server 220 transmits the received display control data for thestatus display selection screen to the Web client 100. The Web client100 displays the screen based on the received display control data forthe status display selection screen.

On this screen, when the user selects logic CORE generation, displaycontrol data without name display of the logic CORE on the logic COREgenerating status screen shown in FIG. 25 is created by the statusdisplay interface program 224, and the display control data istransmitted to the Web server 220. The Web server 220 transmits thereceived display control data for the logic CORE generating statusscreen to the Web client 100. The Web client 100 displays the screenbased on the received display control data for the logic CORE generatingstatus screen.

On this screen, when the user inputs the project name and presses adisplay button, the Web client 100 sends the project name to the Webserver 220. The status display interface program 224, having receivedthe project name from the Web server 220, extracts the directory name ofthe logic CORE in the directory ASIC 50 in FIG. 14 from the directoryhaving the specified project name, updates the display control data forthe logic CORE generating status screen and sends the display controldata to the Web server 220. The Web server 220 sends the receiveddisplay control data for the logic CORE generating status screen to theWeb client 100. The Web client 100 displays the screen based on thereceived display control data for the logic CORE generating statusscreen. On this screen, the directory name of the ASIC logic COREgenerated previously is displayed.

The process procedure on the ASIC logic CORE generating status displayscreen will be explained next, with reference to the flowchart in FIG.26. If the user selects any of the displayed logic COREs and selectsdownload (step S1501), the target logic CORE can be downloaded to theWeb client 100 (step S1502). The downloaded logic CORE can be used forlogic verification as a netlist of the ASIC chip level, and hence it ispossible to debug with focus on the respective functions constitutingthe instance.

On the other hand, if the user specifies the logic CORE name and selectsan FPGA formation button (step S1503), the Web client 100 sends data tothe Web server 220 informing the project name, the logic CORE name, andthat the FPGA formation button has been selected, and the Web server 220sends the received data to the status display interface program 224. Thestatus display interface program 224 extracts a file name of the tabledata in the IO directory under the directory having the target logicCORE name, and the display control data for the FPGA logic COREgenerating interface screen as shown in FIG. 27 is created and sent tothe Web server 220.

The Web server 220 sends the received display control data for the FPGAlogic CORE generating interface screen to the Web client 100. The Webclient 100 displays the screen based on the received display controldata for the FPGA logic CORE generating interface screen (step S1504).On this screen, the specified project name, the logic CORE name, and alist of instance names constituting the logic CORE are listed in a listbox on the left side. On this screen, the target logic CORE can also bechanged, and when the user specifies the project name and the logic COREname, the screen is updated according to the process similar to thatshown in FIG. 25.

Further, the screen is an interface for generating the FPGA logic COREfrom the table data of the instance constituting the logic CORE of thetarget ASIC, and the user specifies an instance from the left list boxand selects an “add” button, to add the instance in the right list box.The instance listed in the right list box becomes one FPGA. When theuser selects an instance, sets an FPGA name, and an FPGA number that isa sequential number for management and a unique integer equal to orlarger than 1, and presses an “execute” button, the Web client 100 sendsthe target project name, the ASIC logic CORE name, the FPGA name, a listof instance names to be formed into FPGA, and the FPGA number to the Webserver 220. The Web server 220 then sends the received data to thestatus display interface program 224.

The status display interface program 224 creates a directory with thespecified FPGA number in the directory FPGA 49 shown in FIG. 14,according to the received list of the instance names, and copies thetable data matching with the name into the directory of the number fromthe IO directory under the directory having the CORE name in thedirectory ASIC 50 in FIG. 14. The FPGA logic CORE generator program 252is then executed by using the list of the table data names as anargument.

The process procedure for the FPGA logic CORE generator program 252 willbe explained below with reference to flowcharts in FIGS. 28 and 29. Theprocessing in FIG. 28 is the same as that shown in FIG. 21, and theprocessing in FIG. 29 is the same as that shown in FIG. 22, except ofstep S1717 and step S1720. Therefore, only these two steps will beexplained.

At step S1017 in FIG. 22, when the instance name to be connected and theoutput port name thereof defined in the port, being an input of thetarget instance, are not present in the information stored in thememory, an error message is output to the log file. However, at stepS1717 in FIG. 29, because the connection between ports of the instancecan be ensured essentially as the ASIC logic CORE, at step S1717, not anerror message, but input terminal information of the package is addedand stored in the memory.

Further, at step 1020 in FIG. 22, finally remaining unconnected portinformation is output to the log file. On the other hand, at step S1720,the target log file in the directory of the ASIC logic CORE created inthe name of “CORE+process ID+date and time” under the directory ASIC 50in FIG. 14 is compared with the log file output at step S1720, and anoutput port, which is not in the log file output at step S1020, is addedand stored in the memory as the output terminal information of thepackage. Thereafter, in the same manner as the processing at step S1020,the logic CORE is output in a file with an FPGA name specified in thedirectory of the specified number under the directory FPGA 51 in FIG.14.

The status display interface program 224 reads the FPGA logic CORE file,counts the number of terminals to be for input and output of thepackage, calculates all the percentage accounted for of the number of IOin the second column in a compatible package table shown in FIG. 30,extracts a package having the largest percentage and the compatiblepackage data thereof, updates the screen display control data having thepackage name and the IO usage rate for the FPGA logic CORE generatinginterface screen shown in FIG. 27 and sends the data to the Web server220. The Web server 220 sends the received display control data for theFPGA logic CORE generating interface screen to the Web client 100, andthe Web client 100 updates the input screen based on the receiveddisplay control data for the FPGA logic CORE generating interfacescreen.

If not satisfied with this result, the user tries again to generate theFPGA logic CORE. If the user selects “determine” (see FIG. 27), the Webclient 100 sends data indicating that “determine” has been selected anddata including the FPGA number, the package name, and the IO usage rate,to the Web server 220. The status display interface program 224 havingreceived these data from the Web server 220 creates a directory having anumber specified in the directory FPGA 55 in FIG. 14, and outputs a fileof the data received, for example, with a name of plist.

The process procedure for the logic synthesis interface program 222 willbe explained. FIG. 31 is a flowchart of the process procedure for thelogic synthesis interface program 222. As shown in FIG. 31, this logicsynthesis interface program 222 sends display control data for a logicsynthesis interface screen as shown in FIG. 32 to the Web server 220.The Web server 220 sends the received display control data for the logicsynthesis interface screen to the Web client 100, and the Web client 100displays the screen based on the received display control data for thelogic synthesis interface screen (step S2001).

When the user specifies a project name, a target logic CORE namedisplayed in FIG. 25, a functional block name to be logic synthesized,and the number of the FPGA to be incorporated, and selects whether togive priority to the area or speed, and whether to Debug (logicsynthesis of the FPGA is not executed) or Fix (logic synthesis of theFPGA is executed) (step S2002), and presses the “execute” button (stepS2003), the Web client 100 displays a data selection screen.

When the user selects an RTL source to be logic synthesized according tothis screen, the Web client 100 sends these data to the Web server 220.The logic synthesis interface program 222, having received the data fromthe Web server 220, creates a directory for the RTL source with a nameof the specified functional block name in the directory ASIC 52 in FIG.14, and stores the RTL (step S2004). The RTL source is then read one byone, to extract operation frequency specified by the user in the headerportion where a change history in the RTL source and the engineeringlevel are described, and the functional block name to be logicsynthesized is specified, by using a frequency obtained by increasing20% with respect to the extracted value, and a logic synthesis conditionof giving priority to the speed or area specified by the user as alimitation for logic synthesis, to execute the ASIC logic synthesisprogram 253 of the ASIC logic synthesis tool (step S2005).

When the ASIC logic synthesis has finished, the logic synthesisinterface program 222 sends a report file output to the directory of thespecified functional block under the directory ASIC 54 in FIG. 14 by theASIC logic synthesis program 253, the user's e-mail address obtained byreferring to the user management server 240 by the project name, and theblock name to the mail server 260, and the mail server 260 transmits ane-mail to the user (step S2006).

The logic synthesis interface program 222 then executes this processingprocess with respect to all RTL sources present in the directory createdin the specified functional block name under the directory ASIC 52 inFIG. 14. When the logic synthesis for all RTL sources has finished (Yesat step S2007), the logic synthesis interface program 222 searches areport of the logic synthesis results for all RTL sources when priorityis given to the speed being specified (Yes as step S2008), anddetermines whether the operation frequency defined in the RTL source issatisfied (steps S2009 to S2010). When priority is given to the areabeing specified, nothing is performed.

It is checked if Fixing is specified (step S2011), and if Fixing isspecified, the logic synthesis interface program 222 creates a directorywith the specified FPGA number under the directory FPGA 55 in FIG. 14,copies and stores the RTL in the specified functional block directoryunder the directory ASIC 52 in FIG. 14 therein, and executes the FPGAlogic synthesis interface program using the specified project name andthe FPGA number as arguments (step S2012).

The logic synthesis interface program 222 activates the logic synthesistool, inputs a command to the logic synthesis tool to read the ASIClogic CORE from the specified logic CORE directory in the directory ASIC50 in FIG. 14, and reads a file defining ASIC package terminalassignment uploaded by the user and existing in the directory ASIC 54 inFIG. 14, and a buffer electrically interfacing with an external deviceconnected to the ASIC. A command is input to the logic synthesis toolaccording to the definition, to insert the ASIC buffer and a testcircuit such as a scan between the terminal of the ASIC logic CORE and apad of a chip connected to the package terminal and to connect these.The data of the functional block in all directories under the directoryASIC 52 in FIG. 14, which has been logic synthesized, is read byinputting a command to the logic synthesis tool and inserted in thelogic CORE, to create a netlist of the ASIC for layout designing, and isthen output in a file with a project name to the directory ASIC 54 inFIG. 14 (step S2013).

The process procedure for the FPGA logic synthesis interface programwill be explained below with reference to the flowchart in FIG. 33. TheFPGA logic synthesis interface program creates a directory with an FPGAnumber specified by the ASIC logic synthesis interface program in thedirectory FPGA 55 in FIG. 14. The RTL source in the directory of thespecified number under the directory FPGA 53 in FIG. 14 is read one byone, to extract operation frequency data defined by the user in theheader portion where a change history in the RTL source and theengineering level are described. The functional block name to be logicsynthesized is specified using a frequency obtained by increasing 20%with respect to the extracted value, to execute the FPGA logic synthesisprogram 254 of the FPGA logic synthesis tool (step S2201).

When FPGA logic synthesis has finished, the FPGA logic synthesis program254 outputs the logic synthesis result to the directory of the relevantnumber in the directory FPGA 55 in FIG. 14 in the name of the functionalblock. The user can proceed with the designing work, while confirmingthe gate usage rate on the logic synthesis status display in FIG. 34(described later). The FPGA logic synthesis program then sends a messageto inform of the end of the logic synthesis, the FPGA number, the blockname, and the user's e-mail address, obtained by referring to the usermanagement server 240 using the project name, to the mail server 260.The mail server 260 transmits an e-mail to the user (step S2202).

The FPGA logic synthesis interface program then confirms whether thelogic synthesis of all functional blocks constituting the FPGA of thespecified number has finished (step S2203). This confirmation isperformed by extracting the functional block name in the directory ofthe relevant number in the directory FPGA 51 in FIG. 14, and comparingwith the functional block name for which the logic synthesis hasfinished. If there is no difference, the FPGA logic synthesis interfaceprogram extracts a file name of the logic CORE, being the FPGA name inthe directory of the relevant number in the directory FPGA 51 in FIG.14, and checks whether a fitting control file defining correspondencebetween a package terminal name, being the same as the port name of theFPGA logic CORE to be used for fitting, and the terminal number, andoperation frequency, being the FPGA layout, is uploaded by the user andis present in the directory FPGA 55 in FIG. 14 (step S2206).

If the file is present, the FPGA logic synthesis interface programspecifies all functional blocks constituting the FPGA, and the FPGAlogic CORE in the directory of the relevant number under the directoryFPGA 51 in FIG. 14, to execute the FPGA logic synthesis program 254.After the logic synthesis of the FPGA, the FPGA logic synthesisinterface program activates the fitting program 255, inputs the netlistobtained as the logic synthesis result to the fitting program 255 toperform layout, creates ROM data recording the circuit information,being the layout result of the FPGA, and outputs the ROM data in theFPGA name to the directory of the relevant number under the directoryROM 46 in FIG. 14 (step S2207). The FPGA logic synthesis interfaceprogram then sends an ending message of ROM data creation, the FPGAnumber, the project name, and the user's e-mail address obtained byreferring to the user management server 240 to the mail server 260, totransmit the e-mail (step S2208).

If the logic synthesis of all functional blocks constituting the FPGA ofthe specified number has not finished (No at step 2203), it isdetermined whether the fitting data has been input and the “execute”button has been pressed on the execution screen (step S2204), and if the“execute” button has not been pressed, the process terminates. However,if the “execute” button has been pressed, HDL description instructing toconnect a flip-flop to all input and output ports, connect all outputports in the flip-flop on the input side to a suitable gate, forexample, an input port of two-input NAND, connect the output of all NANDgates to an input port of a new two-input NAND gate, and repeat such amultistage connection of the two-input NAND, to connect the output ofthe two-input NAND on the last stage to input ports of all flip-flops onthe output side, within the respective functional blocks in the FPGAlogic CORE in the directory of the relevant number under the directoryFPGA 51 in FIG. 14, is inserted into all functional blocks for whichlogic synthesis has not been performed, so that logic synthesis can beperformed (step S2205).

Thereafter, the steps 2206 onwards are executed. Depending on theverification strategy at the time of starting the development, when thefunctional block has a configuration such that it can be functionallydivided largely into upward and downward by the circuit architecturestudy, and when the design of the upward function has been completed byinserting a dummy circuit using a flip-flop or the like, verification ispossible even if the design of the downward function has not beencompleted, thereby considerably contributing to improvement of theverification efficiency.

A logic synthesis status display screen shown in FIG. 34 will beexplained below. When a user selects logic synthesis on the statusdisplay screen shown in FIG. 24 using the Web client 100, the Web client100 sends information indicating that logic synthesis has been selectedto the Web server 220. The status display interface program 224, havingreceived data from the Web server 220, extracts a gate size from thelogic synthesis result in the directories of all numbers under thedirectory FPGA 55 shown in FIG. 14, with respect to all project namesobtained by referring to the user management server 240, with the nameof the user who logged in.

The status display interface program 224 then extracts packageinformation from the plist in the same directory generated by the FPGAlogic CORE generation explained above, selects a package in which thepercentage of the gate size becomes 75% or less in the table shown inFIG. 30, based on the package information, creates display control datafor the logic synthesis status display screen in FIG. 34, and sends thedata to the Web server 220. The Web server 220 sends the display controldata for the logic synthesis status display screen to the Web client100, and the Web client 100 displays the screen based on the receiveddisplay control data for the logic synthesis status display screen.

The reason for selecting a package in which the percentage of the gatesize is 75% or less will be briefly explained. Normally, the FPGA logicsynthesis tool suggests a suitable package and the gate usage rate fromthe database included in the logic synthesis tool, based on the gatesize in the logic synthesis result. However, in fitting of the FPGA, aunit block in which the logic is realized by the FPGA, is used forwiring to increase the wiring efficiency in a cell arranging process.Therefore, 75% is set so that the gate usage rate does not exceed 100%after fitting, which may differ between FPGAs, taking into considerationthat the gate size becomes larger than that of the logic CORE result.Accordingly, it is effective to execute the FPGA logic synthesis foreach functional block.

Input of the fitting data and the execution screen will now beexplained. FIG. 35 is one example of an input and execution screen offitting data. When the user selects fitting on the procedure screenshown in FIG. 18 by using the Web client 100, the Web client 100 sendsinformation indicating that fitting has been selected to the Web server220. The fitting interface program 223, having received the data fromthe Web server 220, extracts numbers and names of all directories underthe directory FPGA 55 in FIG. 14 and a file name of the netlist, thatis, the FPGA name, being the logic synthesis result, in the respectivedirectories, with respect to all project names obtained by referring tothe user management server 240 by the name of the user who logged in,creates display control data for the input and execution screen of thefitting data shown in FIG. 35, and sends the display control data to theWeb server 220.

The Web server 220 sends the display control data for the input andexecution screen of the fitting data to the Web client 100, and the Webclient 100 displays the screen based on the received display controldata for the input and execution screen of the fitting data. Whencondition data input is selected on this screen, the Web client 100displays a data selection screen.

According to this screen, when the user selects fitting control file,the Web client 100 sends the selected FPGA number and the fittingcontrol file to the Web server 220, and the fitting interface program223, having received the data from the Web server 220, stores thefitting control file in the directory of the relevant number under thedirectory FPGA 55 in FIG. 14.

When the user selects the “execute” button, the Web client 100 sendsinformation indicating the selected FPGA number, the project name, andthat execution has been selected, to the Web server 220. The fittinginterface program 223, having received data from the Web server 220,executes the FPGA logic synthesis interface program by using the projectname and the FPGA number as arguments. The process for the FPGA logicsynthesis interface program is as explained above.

A ROM data generating status screen will be explained below. FIG. 36 isone example of the ROM data generating status screen. When the userselects ROM data on the status display selection screen shown in FIG. 24by using the Web client 100, the Web client 100 sends informationindicating that ROM data has been selected, to the Web server 220.

The status display interface program 224, having received data from theWeb server 220, extracts numbers and names of all directories under thedirectory ROM 46 in FIG. 14, and a ROM data name, that is, the FPGAname, being the fitting result in the respective directories, withrespect to all project names obtained by referring to the usermanagement server 240 by the name of the user who logged in, createsdisplay control data for the ROM data generating status screen shown inFIG. 36, and sends the display control data to the Web server 220.

The Web server 220 sends the display control data for the ROM datagenerating status screen to the Web client 100, and the Web client 100displays the screen based on the received display control data for theROM data generating status screen. The user clicks a date part of thetarget FPGA on this screen, to download the ROM data.

The process of the monitoring server 290 will be explained below. Themonitoring server 290 monitors whether there is any change in the RTL,the time required for by logic synthesis, fitting, and the layoutdesigning tool, and the manual operation time required for reflectingthe change, which is the time other than the processing time of the toolused for the implementation design based on the scale of change in thefunctional block defined by a designer.

There is a directory with the project name for each project in thedirectory LAYOUT 47 in FIG. 14 managed by the implementation designer,and the operation is performed therein. There are a LAY directory forstoring layout design data, and an RTL directory for storing the RTLsource in the directories with the respective project names. The RTLdirectory has the same directory configuration as that of the directoryASIC 52 in FIG. 14.

The monitoring server 290 monitors the LAY directory and the RTLdirectory. A schedule reflecting the result of adding up the time isstored with a name of schedule in the directory of the project name, andin the initial state, scheduled date of 1stRTL and scheduled date ofSign Off are set based on matching. 1stRTL is defined as an RTL forwhich layout designing can be started, and at this point in time, thereis no probability of a large change, and about 80% of functionverification has finished. Sign Off denotes the date on which the ASICproduction data is to be delivered to a device vender, after completionof the layout designing of the ASIC.

FIG. 37 is one example of a schedule and result screen. In this figure,a schedule file is converted into screen display control data, anddisplayed by the Web client 100. In other words, when a user selectsresult and schedule on the status display screen in FIG. 24, the Webclient 100 sends information indicating that result and schedule hasbeen selected, to the status display interface program 224 via the Webserver 220. The status display interface program 224, having receivedthe information, converts the schedule file into the screen displaycontrol data, and sends the data to the Web client 100 via the Webserver 220. The Web client 100, having received the screen displaycontrol data, displays the screen based on the screen display controldata.

FIG. 38 is one example of an operation time setting file set by thelayout designer. This file is stored with a name “Manual” in the samedirectory as the schedule file.

When it is time to monitor, the monitoring server 290 obtains the username, the project name to which the user belongs, and the e-mail addressof the user from the user management server 240. The monitoring server290 then reads the schedule file to extract the scheduled date for the1stRTL. When the scheduled date is after the monitoring execution date,the processing finishes without doing anything. When the scheduled dateis before the monitoring execution date, the processing hereafter isexecuted.

At first, if there is no RTL source in the RTL directory in thedirectory of the project name under the LAYOUT directory managed by theimplementation designer, the processing is suspended. If the RTL sourceis present, RTL sources in the directories of the respective blocksunder the directory ASIC 52 in FIG. 14 are compared.

If there is a difference therebetween, the monitoring server 290 sendsthe block name having the difference, the project name, and the e-mailaddress of the implementation designer to the mail server 260, and thesedata are transmitted from the mail server 260 to the implementationdesigner. The implementation designer estimates the time required forreflecting the change according to the e-mail. As a result ofestimation, if necessary, the implementation designer updates, adds, ordeletes the time data in the schedule file.

The monitoring server 290 then extracts a block name constituting theASIC from the ASIC logic CORE having the latest generation time underthe directory ASIC 50 in FIG. 14, and stores the block name in thememory. The monitoring server 290 then extracts the logic synthesisprocessing time from a report file in the logic synthesis result in thedirectories of the respective blocks under the directory ASIC 54 in FIG.14. When there is no report file for the block name stored previously inthe memory, that is, when the logic synthesis has not yet beenperformed, the average of the time extracted from the existing reportfiles is applied to calculate the total time, and the monitoring server290 stores the total time in the memory.

If a file of the timing verification result, being the final step of thelayout designing step, of the layout designing results in the directoryof the project name, is present under the directory LAYOUT 47 in FIG. 14managed by the implementation designer, the processing time is extractedfrom the processing result file output by the tool used in the wholeprocess in layout designing, to calculate the total time, by adding itto the time stored in the memory before. If there is no file of thetiming verification result, the time estimated and set beforehand by thelayout designer in the monitoring server at the time of matching, isapplied.

The monitoring server 290 calculates the total of the total time and thetime set in the manual explained above to calculate the number of days,assuming 12 hours as one day, to update the schedule file, if necessary.In other words, in the initial state, there is only a scheduled date ofthe 1stRTL in the schedule file, and the total time is added to thescheduled date, to add the scheduled date for incorporating the changein the implementation design thereto as a reflection starting date asshown in FIG. 37.

In the next monitoring, if the reflection starting date is after themonitoring execution date, the number of days from the scheduled datefor 1stRTL, being one before the reflection starting date, till thescheduled date set as the reflection starting date is set to be acomparison object. If the reflection starting date is beyond thecalculated number of days required for the implementation designing, thereflection starting date is not updated. When the reflection startingdate is before the monitoring execution date, the monitoring server 290sends the e-mail addresses of the user and the implementation designer,and a message informing that it is time to start reflection, to the mailserver 260. The mail server 260 transmits an e-mail to the user and theimplementation designer. At this time, if the newest reflection startingdate is before the monitoring execution date, and if there is no datewritten in the column of result date for the reflection starting date,the monitoring server 290 does not update the schedule file.

When an e-mail of acknowledgement or of rejection has arrived to themonitoring server 290 from both the user and the implementation designerwith respect to the e-mail message indicating the opportunity to startreflection, and if both the user and the implementation designer sendthe e-mail of acknowledgement, the monitoring server 290 sets the dateon which the e-mail has received in the result date with respect to thereflection starting date in the schedule file. In the next monitoring,if the newest reflection starting date is before the monitoringexecution date, and a date is written in the column of result date forthe reflection starting date, the number of days for implementationdesigning is calculated based on the result date, to add a newreflection starting date. When this process is continued, the reflectionstarting date approaches the Sign Off date.

When the scheduled date for the reflection starting date is calculated,and when it exceeds the Sign Off date, the monitoring server 290 sends amessage informing that the reflection starting date cannot be set, andthe e-mail addresses of the user and the implementation designer to themail server 260, and the mail server 260 transmits the e-mail to theuser and the implementation designer.

When the user has sent an e-mail of rejection with respect to themessage informing that it is the opportunity to start reflection, theWeb client 100 sends a message to the user informing that scheduled dateis set, sends e-mail addresses of the user and the implementationdesigner to the mail server 260, and the mail server 260 transmits thee-mail to the user and the implementation designer.

The schedule and result screen will be explained below. FIG. 37 is oneexample of the schedule and result screen. A logic Fix button and achange button in FIG. 37 are arranged near the newest reflectionstarting date, which is before the monitoring execution date by themonitoring server 290. When the user specifies the date in a datesetting column below the button and presses the change button, the Webclient 100 sends information indicating the set date and that change hasbeen selected to the Web server 220. The status display interfaceprogram 224, having received the data from the Web server 220, changesthe scheduled date for the newest reflection starting date in theschedule file to the specified date, and sends a message indicating thechange, and the e-mail addresses of the user and the implementationdesigner to the mail server 260. The mail server 260 transmits thee-mail to the user and the implementation designer.

When the logic Fix button in FIG. 37 is pressed the date is specified,the status display interface program 224 executes the same process asthat of when the change button is selected, and then suspends monitoringby the monitoring server 290. In this manner, a short-term target forthe user and the implementation designer becomes clear, and theprecision of specifying the scheduled date for the change-starting dateincreases as the number of tries of the implementation designingincreases. Thus, the user and the implementation designer get anopportunity to consider how to proceed. Consequently, the efficiencyimproves considerably.

As described above, in the second embodiment, based on a request of auser from the Web client 100, the ASIC logic synthesis program 253performs logic synthesis of the ASIC, the FPGA logic synthesis program254 performs logic synthesis of the FPGA, the logic synthesis interfaceprogram 222 displays the result of logic synthesis of the ASIC and theFPGA on the Web client 100, and the mail server 260 informs the user byan e-mail, of the start and the result of the ASIC and FPGA logicsynthesis. Consequently, the user can execute logic synthesis at anytime without providing an exclusive operator for the logic synthesis,can maintain uniform logic synthesis quality as if the logic synthesisis performed by the exclusive operator, and can receive information ofstart and result of the logic synthesis by the e-mail, therebyeliminating the necessity of regularly confirming the progress of logicsynthesis with a computer.

According to the second embodiment, the ASIC logic CORE generatorprogram 251 generates a netlist including only the port connectioninformation of a plurality of functional blocks specified by a user fromthe functional blocks constituting the ASIC, in response to a user'srequest from the Web client 100, generates ROM data in which aprogrammable logic device circuit is recorded by fitting data of thelogic synthesized functional block into the netlist created by the FPGAlogic CORE generator program 252, so that the generation result of theROM data generated by the logic CORE generating interface program 221 isdisplayed on a computer and informed to the user by an e-mail from themail server 260. As a result, the user can save load, time and costrequired for generating the ROM data on which the programmable logicdevice circuit is recorded, without providing a development environmentexclusively for the programmable logic device.

According to the second embodiment, when designing of the functionalblock constituting the ASIC specified by a user has not yet beencompleted and there is no circuit data, the FPGA logic CORE generatorprogram 252 creates a netlist with a circuit in which a temporaryflip-flop or the like is used for the input and output terminals of thefunctional block inserted therein. As a result, in the verification byprototyping of the programmable logic device, even if designing of thefunctional block, which is not a target of verification, has not yetbeen completed, verification by prototyping can proceed, therebyimproving the efficiency of verification.

According to the second embodiment, when the monitoring server 290monitors the scale of change between the latest circuit data held by theuser and the circuit data incorporated into the implementation designingby the implementation designer, and if the planned date has approachedbased on the monitoring result and the time required for layout design,the mail server 260 informs the user and the ASIC implementationdesigner by an e-mail that it is time for reflecting the change in theASIC implementation design, and in response to this information, theuser requests suspension by changing the date for reflection.Consequently, the generated change can be efficiently reflected inlayout designing of the ASIC. By setting the timing for reflecting thechange, the user can determine until when the change can be made, andcan review the schedule at an early stage.

As explained above, the following effects due to the present inventioncan be achieved.

According to the invention of one aspect, in a program storage mediumthat stores a program for making a computer execute a method ofgenerating a core (logic core), the quality of port specification of ablock, being an input in the RTL design, is ensured beforehand in theintegrated circuit development. Further, in a large-scale integratedcircuit having many functional blocks and design resources, becauseconnection between blocks can be confirmed beforehand, it can be ensuredthat a chip is assembled without fail.

According to the invention of another aspect, a core (logic core) of theprogrammable logic device is allocated from the ASIC core (logic core),while maintaining connection between blocks. Therefore, if verificationof the programmable logic device using the core (logic core) isperformed, duplication of verification at least in the sameconfiguration can be avoided in the ASIC. Thus, concurrent developmentof the ASIC and the programmable logic device can proceed efficiently.

When inserting the I/O buffer, the chip port information defined in theblock and the chip terminal information can be cross-checked by a unitthat generates a temporary core (logic core) from the chip terminalinformation, and replaces it by a core (logic core) generated from theblock, thereby ensuring the quality of the port specification of theblock and the chip terminal specification.

According to the invention of still another aspect, a netlist includingports of blocks of optional size and number and port connectioninformation can be created.

According to the invention of still another aspect, a chip netlist canbe created from the netlist including ports of blocks of optional sizeand number and port connection information.

According to the invention of still another aspect, in a recordingmedium that stores a program for making a logic synthesis tool execute amethod of generating a core (logic core) of the programmable logicdevice, a decrease in efficiency of debugging such as logic verificationcan be prevented when a net name, from which it is difficult todetermine the function of a port, becomes a port name.

Thus, the circuit architecture can be shared by generating a core (logiccore) from the design document data and newly generating a core (logiccore) for the programmable logic device from the core (logic core), withthe hierarchical structure and the connection information beingpreserved. The circuit data and the net between instances, which do notdepend on the device technology in the instance in which circuit data isinserted therein and function verification has been performed, can avoidre-verification when the ASIC is formed. Further, this avoidsredesigning due to a difference between the ASIC and the programmablelogic device.

According to the present invention, a development method of integratedcircuits that realizes sharing of the architecture and that can avoidredesign and re-verification as much as possible, and a programmablestorage medium storing the development method is provided.

According to the present invention, the functional blocks constitutingthe ASIC are grouped based on the port connection information, and anetlist including the ports of the grouped functional blocks and theport connection information is created as a core (logic core) of theprogrammable logic device. The ASIC logic synthesis data and the logicsynthesis data for the programmable logic device are created from thecircuit data of the functional blocks constituting the ASIC. The logicsynthesis data for the programmable logic device relating to the groupedfunctional blocks is inserted in the created netlist to create ROM datafor evaluating the real machine in which the circuit of the programmablelogic device is recorded. Layout creation of the ASIC and the timingverification are performed concurrently with creation of the ROM datafor evaluating the real machine using the created logic synthesis datafor the ASIC. A change in the circuit data based on the evaluationresult of the real machine using the created ROM data is reflected increation of ASIC layout and timing verification. Consequently, efficientconcurrent development of the ASIC and the programmable logic devicebecomes efficient, thereby reducing the development period of the ASIC.

According to the present invention, the functional blocks constitutingthe ASIC are grouped based on the port connection information, and anetlist including the ports of the grouped functional blocks and theport connection information is created as a core (logic core) of theprogrammable logic device. The ASIC logic synthesis data and the logicsynthesis data for the programmable logic device are created from thecircuit data of the functional blocks constituting the ASIC. The logicsynthesis data for the programmable logic device relating to the groupedfunctional blocks is inserted in the created netlist to create ROM datafor evaluating the real machine in which the circuit of the programmablelogic device is recorded. Layout creation of the ASIC and the timingverification are performed concurrently with creation of the ROM datafor evaluating the real machine using the created logic synthesis datafor the ASIC. Consequently, concurrent development of the ASIC and theprogrammable logic device becomes efficient, thereby reducing thedevelopment period of the ASIC.

According to the present invention, logic synthesis of the ASIC isexecuted in response to a user's request, it is determined whether thelogic synthesis result of the formed ASIC satisfies the speedperformance requested by the user. Logic synthesis of the programmablelogic device is executed based on the determination result. Theexecution result of logic synthesis of the ASIC and the execution resultof logic synthesis of the programmable logic device are displayed on acomputer, and an e-mail informing execution start and execution resultof logic synthesis of the ASIC, and execution start and execution resultof logic synthesis of the programmable logic device is sent to the user.Consequently, the user can execute logic synthesis at any time withoutproviding an exclusive operator for the logic synthesis, can maintainuniform logic synthesis quality as if the logic synthesis is performedby the exclusive operator, and can receive information of start andresult of the logic synthesis by the e-mail, thereby eliminating thenecessity of regularly confirming the progress of logic synthesis by acomputer.

According to the present invention, a netlist including the portconnection information of a plurality of functional blocks specified bya user from the functional blocks constituting the ASIC is created inresponse to a user's request. ROM data in which a programmable logicdevice circuit is recorded is generated by inserting data of the logicsynthesized functional block in the created netlist, and the generationresult of the generated ROM data is displayed on a computer, andinformed to the user by an e-mail. Consequently, the user can save load,time and cost required for generating the ROM data in which theprogrammable logic device circuit is recorded, without providing adevelopment environment exclusively for the programmable logic device.

According to the present invention, when designing of the functionalblock constituting the ASIC specified by a user has not yet beencompleted and there is no circuit data, a netlist with a circuit inwhich a temporary flip-flop or the like is used for the input and outputterminals of the functional block inserted therein is created.Consequently, in the verification by prototyping of the programmablelogic device, even if designing of the functional block, which is not atarget of verification, has not yet been completed, verification byprototyping can proceed, thereby improving the efficiency ofverification.

According to the present invention, when the scale of change between thelatest circuit data held by the user and the circuit data incorporatedinto the implementation designing by the implementation designer ismonitored, and approaches the planned date based on the monitoringresult and the time required for layout design, the user and the ASICimplementation designer are informed by an e-mail of the change and thatit is time for reflecting the change in the ASIC implementation design.In response to this information, the user requests suspension bychanging the date for reflection. Thus, the generated change isreflected efficiently in layout designing of the ASIC. By setting thetiming for reflecting the change, the user can determine until when thechange can be made, and can review the schedule at an early stage.

Further, according to the present invention, to create a netlist for theFPGA and the ASIC, on the one hand, FPGA design information is createdin which the same terminals in a first design and a second design areconnected, and a buffer corresponding to the FPGA is inserted betweenthe terminals, from the first design in which terminal information ofthe FPGA including the whole or a part of functional blocks of aplurality of functional blocks is described, and the second design inwhich the same terminal information as that of the FPGA described as alow-order layer of the first design is described, and on the other hand,ASIC design information is created in which the same terminals in athird design and a fourth design are connected, and a buffercorresponding to the ASIC is inserted between the terminals, from thethird design in which terminal information of the ASIC including thefunctional blocks is described, and the fourth design in which the sameterminal information as that of the ASIC described as a low-order layerof the third design is described. This is followed by replacing each ofthe second design and the fourth design by the circuit informationcreated based on the connection information of the functional blocksincluded in each design. Consequently, efficient concurrent developmentof the ASIC and the programmable logic device becomes possible, therebyreducing the development period of the ASIC.

INDUSTRIAL APPLICABILITY

As described above, the development method of integrated circuits, theprogram storage medium storing the development method of integratedcircuits, and the concurrent development system, concurrent developmentprogram, and concurrent development method of the ASIC and theprogrammable logic device according to the present invention aresuitable for development of integrated circuits, and particularlysuitable for development of the ASIC and the programmable logic device.

1. A concurrent development system for concurrent development of an ASICand a programmable logic device used by a user from a computer connectedto a network, comprising: an ASIC logic synthesis unit that executeslogic synthesis of the ASIC in response to a request from the user, toobtain a first logic synthesis result; an ASIC logic synthesis resultdetermining unit that determines whether the first logic synthesisresult satisfies a speed performance required by the user, to obtain adetermination result; a programmable logic device logic synthesis unitthat executes logic synthesis of the programmable logic device, based onthe determination result to obtain a second logic synthesis result; alogic synthesis result displaying unit that displays the first logicsynthesis result and the second logic synthesis result on the computer;and a logic synthesis informing unit that informs the user by an e-mail,of start of the logic synthesis of the ASIC and the first logicsynthesis result, and of start of the logic synthesis of theprogrammable logic device and the second logic synthesis result.
 2. Theconcurrent development system for concurrent development of an ASIC anda programmable logic device according to claim 1, further comprising: anetlist creating unit that creates a netlist including port connectioninformation of a plurality of functional blocks specified by the user,from functional blocks constituting the ASIC, in response to a requestof the user; a ROM data creating unit that creates ROM data, in which acircuit of the programmable logic device is recorded, by inserting logicsynthesized data of the plurality of functional blocks into the netlistcreated by the netlist creating unit; a ROM data creation result displayunit that displays a result of the creation of the ROM data, on thecomputer; and a ROM data creation result informing unit that informs theuser by an e-mail, of the result of creation of the ROM data.
 3. Theconcurrent development system for concurrent development of an ASIC anda programmable logic device according to claim 2, further comprising: atemporary netlist creating unit that creates a netlist in which a dummycircuit is inserted in an input terminal and an output terminal of thefunctional block constituting the ASIC specified by the user, whendesigning of the functional block has not been completed, and when thereis no circuit data.
 4. The concurrent development system for concurrentdevelopment of an ASIC and a programmable logic device according toclaim 1, further comprising: a monitoring unit that monitors the latestcircuit data the user has and the scale of change in the circuit dataincorporated in an implementation design by an implementation designer,to thereby obtain a monitoring result; a change timing informing unitthat informs the user and the implementation designer of the ASIC by ane-mail that it is time to reflect the change monitored, based on themonitoring result and the time required for the layout designing, at ascheduled date and time; and a reflection suspension requesting unitusing which the user requests suspension of reflecting the changemonitored, by altering the date for reflecting the change monitored, inresponse to the e-mail.
 5. A concurrent development method forconcurrent development of an ASIC and a programmable logic device usedby a user from a computer connected to a network, comprising: a firstexecuting including executing, by using a computer, logic synthesis ofthe ASIC in response to a request from the user, to obtain a first logicsynthesis result; determining whether the first logic synthesis resultsatisfies a speed performance required by the user, to obtain adetermination result; a second executing including executing logicsynthesis of the programmable logic device, based on the determinationresult to obtain a second logic synthesis result; displaying the firstlogic synthesis result and the second logic synthesis result on thecomputer; and informing the user by an e-mail, of start of the firstexecuting and the first logic synthesis result, and of start of thesecond executing and the second logic synthesis result.